Forward request headers

[jwoyame]

To behave more like a "true" HTTP proxy, the scripts could forward all request headers from the browser which are not explicitly set by the script itself.

This would enable features such as:

• "If Modified" requests
• Partial range requests
• Cookies
• Better request logging on the destination server (e.g. User-Agent)

It would also help to prevent unforeseen issues and bugs, such as the (fixed) issue where PDF files could not be proxied due to the "Range" header getting dropped by the proxy.

[bsvensson]

I think this is similar to what we added for JSP recently: #164 and I think this is how all three proxies should behave.

[jwoyame]

The "copyHeaders" function of the DotNet proxy will copy the original response headers to the final response. Doing the same for the request headers seems to make sense. I would be willing to tackle this enhancement for the DotNet version if needed.

[bsvensson]

Thanks @jwoyame that would be great if you could "tackle" the DotNet for this. Meanwhile I've merged in #174 even though I assume that will become irrelevant once this get implemented.

[jwoyame]

Okay! You are right, #174 is not a good permanent solution.

[cheetah90]

I think now we are forwarding all the headers from the client request. Right? @bsvensson

[jwoyame]

I implemented the upgrade in the unaccepted pull request #186, the issue is still worth review. Headers are copied for responses but not for requests.

[bsvensson]

This has been fixed and merged - see #433.