[ 
https://issues.apache.org/jira/browse/TS-4809?focusedWorklogId=27966&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-27966
 ]

ASF GitHub Bot logged work on TS-4809:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Sep/16 19:33
            Start Date: 02/Sep/16 19:33
    Worklog Time Spent: 10m 
      Work Description: Github user atsci commented on the issue:

    https://github.com/apache/trafficserver/pull/960
  
    FreeBSD build *successful*! See 
https://ci.trafficserver.apache.org/job/Github-FreeBSD/685/ for details.
     



Issue Time Tracking
-------------------

    Worklog Id:     (was: 27966)
    Time Spent: 1h  (was: 50m)

> [header_rewrite] check to make sure "hook" conditions are first in the rule 
> set 
> --------------------------------------------------------------------------------
>
>                 Key: TS-4809
>                 URL: https://issues.apache.org/jira/browse/TS-4809
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Plugins
>            Reporter: Gancho Tenev
>            Assignee: Gancho Tenev
>             Fix For: 7.0.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The following configuration
> {code}
> $ cat etc/trafficserver/remap.config
> map http://example.com http://127.0.0.1:8888 \
>     @plugin=header_rewrite.so @pparam=hdrs.config
> $ cat etc/trafficserver/hdrs.config
> cond %{TRUE}
> cond %{REMAP_PSEUDO_HOOK}
>    set-header Some-Header "some value"
> {code}
> Triggers the following error which does not show what and where the problem 
> is:
> {code}
> 20160901.23h17m13s [header_rewrite] Unknown condition: REMAP_PSEUDO_HOOK
> {code}
> I would like to add a check which will prevent the above error and print 
> another error clarifying where and what the problem is, for instance:
> {code}
> 20160901.23h17m13s [header_rewrite] cond %{REMAP_PSEUDO_HOOK} should come 
> first in the rule set at hdrs.config:2
> {code}



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

Reply via email to