[
https://issues.apache.org/jira/browse/TS-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095287#comment-15095287
]
ASF GitHub Bot commented on TS-4081:
------------------------------------
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/418
TS-4081 Adds --pristine to use pristine URL on escalation
This new options lets the escalation plugin use the pristine (unmapped) URL
when retrying the request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-4081
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/418.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 #418
----
commit f6ada99b4379b78f1c0ccda94f085e3f7eb9e47b
Author: Leif Hedstrom <[email protected]>
Date: 2015-12-17T00:47:55Z
TS-4081 Adds --pristine to use pristine URL on escalation
----
> Allow escalate plugin to use the pristine URL when retrying
> -----------------------------------------------------------
>
> Key: TS-4081
> URL: https://issues.apache.org/jira/browse/TS-4081
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Labels: A
> Fix For: 6.2.0
>
>
> We have a use case where the remap rules must modify the path for the primary
> origin, but when escalating (using escalate.so) it must use the original
> (pristine) URL. I have a patch which adds a --pristine option to the plugin,
> telling it to base the escalated request on the pristine URL and not the
> remapped URL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
