Backport support for http statusMessage to 0.10.x

[Pavel Strashkin]

Hi there,

I'm wondering whether it's possible to backport a35a2f0192f78c762ed1009025e673cf09862d4d from 0.12.x to 0.10.x. There are few reasons "why":

1. There are enterprise REST APIs that prefer to leverage HTTP status codes >5xx with custom status messages

2. Most of high level node.js HTTP client libraries, including superagent, are based on "http" core module, which means it's impossible to add a support to those libraries until it's supported by core modules. Another option is to re-implement HTTP parser in JS, which is overkill.

3. Due to nature of business and applications most people are developing for enterprise it's very difficult to switch from 0.10.x to 0.12.x in the nearest feature, but having access to that status message is still very important for seamless integration with some of REST APIs.

4. Status message has been part of HTTP spec forever and it's kind of sad it's been missing in the core since the day one :)

Thanks!

[julien...@joyent.com]

Hi Pavel!

On Tuesday, March 17, 2015 at 9:58:27 PM UTC-7, Pavel Strashkin wrote:

I'm wondering whether it's possible to backport a35a2f0192f78c762ed1009025e673cf09862d4d from 0.12.x to 0.10.x. There are few reasons "why":

Could you please file an issue in Node.js' issues tracker here: https://github.com/joyent/node/issues? It will be much easier to discuss it over there.

Thank you!

Julien