I mean, use the manual client as a fallback. It's only as good/hard as you need it to be. You could simply look for the first instance of "\r\n\r\n" and assume everything after that is the body. If you needed the headers, just split on "\r\n" and then split on ":" and you'll get most of it.
Depending on where node fails you might be able to use the underlying http_parser bindings directly. Look in http.js in the node source to see how it's used. On Tue, Jan 8, 2013 at 1:36 PM, Matt <hel...@gmail.com> wrote: > On Tue, Jan 8, 2013 at 2:26 PM, Tim Caswell <t...@creationix.com> wrote: > >> You can use the TCP client directly and hand-roll the http request. Your >> response won't be parsed as http (nor would you want to in the error case), >> but you can write a crude parser in js to get the bulk of it. >> > > Yeah that occurred to me - but seems like a lot of work for one URL at one > provider, where everything else works fine. If the http parser were written > in JS I could probably monkey-patch something at least. > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
