On Fri, Jun 21, 2013 at 12:26 AM, Raymond Feng <[email protected]>wrote:
> I ran into the same issue recently. In my case, the Content-Length is set > to 0. Maybe the http server can do some check (if possible) to report a > more meaningful error? Just to be clear, this is a http *client* issue, not server. We're doing web scraping so deal with a lot of weird broken shit (another one was "Content-Length: 123456,123456" - i.e. the length repeated twice separated by a comma - that comes from Shaw Direct's http servers). Matt. -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
