[
https://issues.apache.org/jira/browse/TS-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919558#comment-13919558
]
Anil Kumar Myla commented on TS-2609:
-------------------------------------
When we have plugin chaining mapToUrl can be different from requestUrl. Let's
say we have a regex plugin before the header rewrite plugin, and the regex
plugin rewrites it to regex.x.y.com instead of the origin.x.y.com
map x.y.com origin.x.y.com <regex plugin> <header rewrite plugin>
_rri->mapToUrl = origin.x.y.com/request_url
_rri->requestUrl = regex.x.y.com/regex_modified_url
You are right, these would ideally be
%{URL:Host}
%{CLIENT-URL:Host}
But from the plugin documentation, I'm thinking the URL/CLIENT-URL conditions
have already been broken down into SCHEME (unimplemented), HOST, PORT
(unimplemented), PATH ,QUERY conditions. Do we really need the URL/CLIENT-URL
conditions ? :)
Let me know what you think.
> Header rewrite plugin TOHOST condition
> --------------------------------------
>
> Key: TS-2609
> URL: https://issues.apache.org/jira/browse/TS-2609
> Project: Traffic Server
> Issue Type: Improvement
> Components: Plugins
> Reporter: Anil Kumar Myla
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 5.0.0
>
>
> Enhance header rewrite plugin to support TOHOST condition. Header rewrites
> conditioned on the final origin server will be supported.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
