-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passing options object to http.createServer stops server responding #24105
Comments
@nodejs/http |
Lines 1779 to 1786 in bd8c107
In fact, The |
Looks like it was backported for v8.12.0: and from the Release notes from v8.12.0:
|
Yeah, but the code of Lines 33 to 35 in 26d145a
I'm not sure if I have missed something. |
Ah, apparently the http change got backed out of the merge for v8.12.0: #20456 (comment) |
As expected given this is not a valid signature for that function. |
Well there is still an issue here... either:
|
@brokencube Thanks for an update. That's helpful in moving this forward. I'm going to reopen and assign the appropriate labels. |
landed in v8.x-staging |
Example:
# telnet localhost 4000 GET /
Expected: Console.log of "got here"
Actual: No output.
It also doesn't work is options is set to:
Is working as expected in v10.13.0
Using
node inspect
the difference in execution between v8 and v10 seems to be this line:_http_common.js:117
return parser.onIncoming(parser.incoming, shouldKeepAlive);
Which should be returning a IncomingMessage object, but instead returns nothing. But that's as far as I could get with this.
Calling without the options object - i.e.:
Works as expected
The text was updated successfully, but these errors were encountered: