[TS-2983] request headers, http object corrupted in 5.0.x

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 5.1.0
• Fix Version/s: 5.1.0
• Component/s: Core
• Assignee: Alan M. Carroll
• Reporter: Sudheer Vinukonda
• Created: 02/Aug/14 17:42
• Updated: 18/Dec/14 05:03
• Resolved: 22/Aug/14 17:16

Description

We have run into a http header/field corruption issue on our proxy infrastructure production hosts when we enabled 5.0.x. The issue results in host header/method and other field corruption.

For example, this is what we see in our squid access logs:

1406999819.698 0 69.109.120.92 ERR_CONNECT_FAIL 404 0 nas=0&disclaimer=2; https://AMCV_att1=xxxxxxxxxxxxxxxxx;%20ypcdb=xxxxxxxxxxxxxxxxxx - NONE/- - 

After a lot of debugging, figured that the request was getting corrupted even before remap and in fact, is being parsed incorrectly at the read request state. Further analysis lead me to the commit TS-2197 (commit 30fcc2b2e698831d1a9e4db1474d8cfc202818a3 in Oct'13), which has altered the way the request is read slightly. Reverting the commit seems to have fixed the issue.

Issue Links

• is related to: TS-2751 remove ProtocolNetAccept