You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Thach Tran (JIRA)" <ji...@apache.org> on 2013/05/02 15:04:15 UTC

[jira] [Commented] (TS-1868) TSREMAP_NO_REMAP_STOP/TSREMAP_DID_REMAP_STOP do not stop remap plugin evaluation chain

    [ https://issues.apache.org/jira/browse/TS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647496#comment-13647496 ] 

Thach Tran commented on TS-1868:
--------------------------------

If this is intended behaviour, then the documentation for remap api could do with a bit more clarification on what will happen with different return codes of a remap plugin as it completely confuses me in this case.
                
> TSREMAP_NO_REMAP_STOP/TSREMAP_DID_REMAP_STOP do not stop remap plugin evaluation chain
> --------------------------------------------------------------------------------------
>
>                 Key: TS-1868
>                 URL: https://issues.apache.org/jira/browse/TS-1868
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Remap API
>            Reporter: Thach Tran
>         Attachments: remap1.c, remap2.c, remap.config
>
>
> I have several remap plugins that I want to combine in a single remap rule. According to the doc, I can chain them in remap.config and if one remap plugin return TSREMAP_NO_REMAP_STOP or TSREMAP_DID_REMAP_STOP, the evaluation chain will be broken (no further plugin down the chain gets to run).
> However, I have found out that this is not the case. All remap plugins in the chain will run regardless of plugins' return code. The only time I see it breaks the chain is if a plugin specifies that it wants to return a redirection response to the mapped url.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira