Bug 45007 - Rewrite Location headers when using Proxy HTTPS spoofing
Summary: Rewrite Location headers when using Proxy HTTPS spoofing
Alias: None
Product: JMeter
Classification: Unclassified
Component: HTTP (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Depends on:
Reported: 2008-05-15 07:08 UTC by Ralf Hauser
Modified: 2008-05-29 06:29 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Hauser 2008-05-15 07:08:00 UTC
as per Bug 7378 comment 10

"Attempt HTTPS Spoofing" nicely rewrites the payload of a http response, but the headers e.g. in 302 was forgotten.

Probably this has some side effects on other header attributes like content-length,  ... but mostly not major.
Comment 1 Sebb 2008-05-15 08:50:46 UTC
Not sure I understand what you mean.

Can you provide a bit more detail please?
Comment 2 Michael Tschannen 2008-05-29 02:43:54 UTC
It should work if
    org.apache.jmeter.protocol.http.proxy.massageResponseHeaders(SampleResult res)
would also replace all "HTTP" with "HTTPS", so (non-relative) redirects (HTTP 302) would also work while spoofing HTTPS. 
Comment 3 Sebb 2008-05-29 03:25:32 UTC
So are you referring to the Location: header?
Comment 4 Michael Tschannen 2008-05-29 03:39:43 UTC
Comment 5 Sebb 2008-05-29 06:23:06 UTC
Fixed in SVN:

URL: http://svn.apache.org/viewvc?rev=661329&view=rev
Bug 45007 - Rewrite Location headers when using Proxy HTTPS spoofing
Use CRLF rather than LF for header lines in Proxy response to client

TODO: fixup content length if page was changed
Comment 6 Sebb 2008-05-29 06:29:02 UTC
URL: http://svn.apache.org/viewvc?rev=661330&view=rev
Bug 45007 - fix content length header if content may have been changed