Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

Node crashing on certain HTTP client request... #242

Closed
TooTallNate opened this issue Aug 17, 2010 · 5 comments
Closed

Node crashing on certain HTTP client request... #242

TooTallNate opened this issue Aug 17, 2010 · 5 comments

Comments

@TooTallNate
Copy link

Hi, see:
http://groups.google.com/group/nodejs/browse_thread/thread/e9ebb73ed64b52a3
or
http://gist.github.com/531588

Essentially, Node is just plain crashing while trying to parse the HTTP response from the remote server. Someone on the mailing list said that it worked with "v0.1.102", but I'm on "v0.1.104" and below is the result:

events:12
        throw arguments[1];
                       ^
Error: Parse Error
    at Client.ondata (http:882:22)
    at IOWatcher.callback (net:517:29)
    at node.js:773:9

Edit: I just tried on my other OS X machine which is running "v0.1.102", and I'm getting the same result...
@polotek
Copy link

polotek commented Aug 18, 2010

This works for me on os x 10.6 with node 0.1.102. It doesn't error. I do get the error consistently on 0.1.104 on the same machine. Also try curl -I (HEAD call). It makes my terminal bug out and does some weird stuff. Probably bad headers.

@TooTallNate
Copy link
Author

I've updated the gist with two Wireshark dumps for comparison:
1 from Node (v0.2.0)
1 from Curl command line

They can be opened up by Wireshark itself to use it's GUI. In Node, the response is coming back from the server, but Node is choking while parsing. It'd think this would be a pretty easy fix, and it's preventing me from using this service in my Node app currently!

Please somebody fix it!

@alexkwolfe
Copy link

I'm seeing this same problem on Node 0.2.0 on Mac OS 10.6.4.

@ry
Copy link

ry commented Mar 21, 2011

this is very old. closing. open a new bug if it's persisting

@ry ry closed this as completed Mar 21, 2011
@TooTallNate
Copy link
Author

a66c61c190a90653da3fd7c1443a1a7329472567 of the http_parser fixed this case. This can remain closed :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ry @alexkwolfe @TooTallNate @polotek