Investigations show that there is a compression issue... Half of the time, the response has a content-encoding set to gzip, and neither http.request nor request module seem to have a native unzip system. I tried to set accept-encoding headers to 'identity' or even to 'identity;q=1, gzip;q=0' but it seems the server hosting the webpage doesn't look at headers before answering! I guess I'll have to implement myself the check of content-encoding and use the node zlib library in this case... (it doesn't have all the decompress tools yet)
On Friday, January 18, 2013 11:17:55 AM UTC+1, Sébastien wrote: > > Hello everyone, > I have a very strange issue, and I can't figure out why: I'm trying to > emit a http request on an external webpage ( > http://www.maisonsdumonde.com/FR/fr/produits/fiche/lit-marron-zen-117200.htm) > with both tools, the native http.request and the request package. > For the test, I do not specify any encoding, bu I also tried with utf8, > binary, or buffer (encoding = null in request package). > > The statuscode is 200, and I receive a body, but in nearly half of the > time, the body looks like : > \u001f?\b\u0000\u0000\u0000\u0000\u0000\u0000\u0003???n\u001cI?(?>???\u000f??R\u0017?\u0019??$?A?"Q??x??\u000e????\u0019ddDVD&)?W\u0001\u001b?\u0017\u0006\u0018`?9@?Us\u0006\u001b\u0018`⌂?\u0016?G... > > (length: 29964) > > instead of : <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 > Transitional//EN"\n "http://www.w3.... (length: 153311) > > Result is I can't do anything with this bad encoded body... > > Do you have an idea? > Thanks a lot!!! > > S. > -- 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
