Sven Van Caekenberghe wrote: > > On 01 May 2011, at 04:28, [email protected] wrote: > >> ZnHttpClient is sending a Connection: close header in the request which >> is causing delicious to return the headers, but not the actual content >> entity. >> >> It's doing this in ZnHttpClient>>method:for:headers:data:limit:. >> Commenting out 'request setConnectionClose' in that method allows the get >> request to work. > > Actually it is a deeper bug, related to what Esteban reported. As far as I > can tell right now, certain servers respond to requests with 'Connection: > Close' by not including a 'Content-Length' (most notably Google GWS, but > apparently other too). The idea is then to read the content #upToEnd. > ZnEntityReader does have a provision for that, but somehow it got disabled > because this behavior is not very common (as far as I remember, but I have > to check again, 'Content-Length' is required with HTTP/1.1, but there > might be finer points in the specs). Enabling it with #allowReadingUpToEnd > should have fixed it, but seems to break lots of other code. I have to > investigate this further. > > Anyway, I now know where to look, so I'll get there. > > Sven >
OK, given what you - and Matt - have found, I think I will wait until you have a tweaked version of the code. In the meantime, it looks like the existing HttpClient will have to suffice - I am trying to do some screen scraping of Delicious, so I really need something that will work with that server. Cheers Andy -- View this message in context: http://forum.world.st/Strange-results-from-Zinc-for-the-www-delicious-com-domain-tp3486942p3488803.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
