[ https://issues.apache.org/jira/browse/TS-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan M. Carroll reassigned TS-2933: ----------------------------------- Assignee: Alan M. Carroll > Using TSHttpTxnEffectiveUrlStringGet() in a remap plugin can mess up > destination port > ------------------------------------------------------------------------------------- > > Key: TS-2933 > URL: https://issues.apache.org/jira/browse/TS-2933 > Project: Traffic Server > Issue Type: Bug > Components: Core, TS API > Reporter: Leif Hedstrom > Assignee: Alan M. Carroll > Fix For: 5.1.0 > > > With a remap rule like > {code} > map http://example.com https://real.example.com @plugin=cacheurl.so > @pparam=cachekey.config > {code} > (note the mapping from http -> https), we'll end up with a request on port 80 > to the origin server. I've verified that the offending API that causes this > "rewrite" is TSHttpTxnEffectiveUrlStringGet() (100% certain). So it's not a > bug in the cacheurl plugin IMO; it does the right thing and returns > TSREMAP_NO_REMAP to tell the rewrite engine to use the default mapping rule. > This mostly works, where the destination host and path are rewritten > properly, but the port gets set to 80 (presumably some default tripping). -- This message was sent by Atlassian JIRA (v6.2#6252)