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

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

                Author: ASF GitHub Bot
            Created on: 20/Jul/16 16:12
            Start Date: 20/Jul/16 16:12
    Worklog Time Spent: 10m 
      Work Description: GitHub user zwoop opened a pull request:

    https://github.com/apache/trafficserver/pull/818

    TS-4683 Adds better error handling on config problems

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zwoop/trafficserver TS-4683

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/818.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #818
    
----
commit 983e4c469805950d9c8a68bc1de35aabf112ed7e
Author: Leif Hedstrom <zw...@apache.org>
Date:   2016-07-19T03:45:21Z

    TS-4683 Adds better error handling on config problems

----


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

            Worklog Id:     (was: 25764)
            Time Spent: 10m
    Remaining Estimate: 0h

> header_rewrite: warning if you use a hook that predates "remap" in a remap 
> mode
> -------------------------------------------------------------------------------
>
>                 Key: TS-4683
>                 URL: https://issues.apache.org/jira/browse/TS-4683
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Plugins
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 7.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> It's rather confusing, but since remap happens after several of the hooks 
> that header_rewrite supports (in global mode), we should warn the user that 
> this is a no-op (or maybe even error out).



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

Reply via email to