[jira] [Updated] (TS-4081) Allow escalate plugin to use the pristine URL when retrying

2016-01-12 Thread Leif Hedstrom (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-4081:
--
Fix Version/s: (was: 6.2.0)
   6.1.0

> 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.1.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)


[jira] [Updated] (TS-4081) Allow escalate plugin to use the pristine URL when retrying

2016-01-06 Thread Leif Hedstrom (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-4081:
--
Fix Version/s: (was: 6.1.0)
   6.2.0

> 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)


[jira] [Updated] (TS-4081) Allow escalate plugin to use the pristine URL when retrying

2015-12-15 Thread Leif Hedstrom (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-4081:
--
Fix Version/s: 6.1.0

> 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
>  Labels: A
> Fix For: 6.1.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)


[jira] [Updated] (TS-4081) Allow escalate plugin to use the pristine URL when retrying

2015-12-15 Thread Leif Hedstrom (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-4081:
--
Labels: A  (was: )

> 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.1.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)