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.
Not sure I understand what you mean. Can you provide a bit more detail please?
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.
So are you referring to the Location: header?
Yes
Fixed in SVN: URL: http://svn.apache.org/viewvc?rev=661329&view=rev Log: 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
URL: http://svn.apache.org/viewvc?rev=661330&view=rev Log: Bug 45007 - fix content length header if content may have been changed
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2113