Ability to use ClientResponse header directly for ServerResponse header

[nathanwdavis]

I am working on something that will need to do a reverse proxy request in some cases. It would be nice to be able to simply pipe the ClientResponse headers into the ServerResponse headers somehow. Currently you have to deal with two conversions:

• lowercase to correct mixed case header names,
• conversion between array-type values to their correct string representation

Since the http request parser converts the header data before _addHeaderLine is even called, the raw data is gone by the time the ClientResponse callback happens.

Sstephenson's proposed fix / pull request (#259) would fix this in a pretty graceful way (I think). Or if there is another more elegant and efficient way to do this, I'd love to hear it.

I don't mind working on a patch if there is interest in this.

[nathanwdavis]

Having a rawHeaders getter on ClientResponse and ServerResponse also could be useful for monitoring/auditing tools.

[joeferner]

I see that this is a year old but are there any plans on fixing this? I am writing a proxy as well and have found an instance of a mobile app which doesn't like the lowercase headers (specifically lowercase "location" header). I know that according to the HTTP standard it shouldn't matter unfortunately people don't always play by the standards.

One possible fix could be to at least move the "toLowerCase" into "_addHeaderLine" so that it would be easier to patch by overriding that function in the "IncomingMessage" prototype.

[chrisdickinson]

It looks like this was addressed by #5999, which was merged and will be coming in v0.12.