You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Peter Chou (JIRA)" <ji...@apache.org> on 2016/05/02 21:21:13 UTC

[jira] [Comment Edited] (TS-4411) Add a error message on unrecognized remap.config @... option.

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

Peter Chou edited comment on TS-4411 at 5/2/16 7:21 PM:
--------------------------------------------------------

I opened a PR with the patch. It is just a one-liner that prints a diagnostic message to the error.log. I did notice that the remap_check_option() is apparently run three times on start-up so the message is printed three times. I did not attempt to squash this as it should be a rare exception condition.


was (Author: pbchou):
I opened a PR with the patch. It is just a one-liner that prints a diagnostic message to the error.log. I did not notice that the remap_check_option() is apparently run three times on start-up so the message is printed three times. I did not attempt to squash this as it should be a rare exception condition.

> Add a error message on unrecognized remap.config @... option.
> -------------------------------------------------------------
>
>                 Key: TS-4411
>                 URL: https://issues.apache.org/jira/browse/TS-4411
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Peter Chou
>            Assignee: Peter Chou
>              Labels: review
>             Fix For: 7.0.0
>
>
> We noticed that unrecognized remap.config options seem to result in "silent" failures, i.e., the remap rule "map /a /b @foo" just reduces to a plain "map /a /b" rule. This is not desirable when we are implementing access control and other functionality in the rule's plugin chain.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)