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 14:56:19 UTC

[jira] [Updated] (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:all-tabpanel ]

Thach Tran updated TS-1868:
---------------------------

    Attachment: remap.config
                remap2.c
                remap1.c

To reproduce, I have included two example remap plugins and a remap.config file that uses those two plugins (assuming they get compiled into remap_example_1.so and remap_example_2.so).

If one enables the debug tag 'remap.*', one should be able to see that both plugins get run on every request even though the first plugin always returns TSREMAP_DID_REMAP_STOP.
                
> 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