keeping case for HTTP headers

[Guatom]

Dear reviewer:

I'll start by saying that this is "fix" for a problem I have related to the SOAP web services I need to invoke. My main problem is that http (via request) lowercases the header names, and the web services I invoke have a case-sensitive validation on http headers:

https://github.com/nodejs/node/blob/master/lib/_http_outgoing.js#L365

I could try to remove that, but I have a strong suspicion that a PR modifying that would be rejected since the HTTP standard states that the HTTP header name validation should be case insensitive:

https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html

I know those WS are not doing what's right, but I'd be surprised if I were the first one having this problem.

Thanks for reading and reviewing.

[slnode]

Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test."

[slnode]

Can one of the admins verify this patch?

[raymondfeng]

@Guatom Thank you for the patch. A few comments:

1. Based on https://github.com/nodejs/node/blob/master/lib/_http_outgoing.js#L365, the header names will be always converted to lower case. How can we keep case-sensitive header names in strong-soap?
2. Your change allows http headers to be passed from options. I don't understand why it helps casing.
3. Please separate code style changes (if needed) in separate commits.
4. Can you add a test case so that we can better understand your proposal and the code have better test coverage?

[slnode]

Can one of the admins verify this patch?

[Guatom]

@raymondfeng: I'll be submitting a detailed explanation of everything.