[TS-2933] Using TSHttpTxnEffectiveUrlStringGet() in a remap plugin can mess up destination port

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.1.0
• Component/s: Core, TS API
• Assignee: Alan M. Carroll
• Reporter: Leif Hedstrom
• Created: 10/Jul/14 20:03
• Updated: 10/Sep/15 15:10
• Resolved: 17/Aug/14 00:10

Description

With a remap rule like

map http://example.com https://real.example.com @plugin=cacheurl.so @pparam=cachekey.config

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

Issue Links

• relates to: TS-3018 Client Request's default port can't be changed after scheme was changed
• relates to: TS-3901 Leaking connections from HttpSessionManager