May 2011 - Pharo-users - lists.pharo.org

Re: [Pharo-users] WebClient for 1.2.2?

by Andy Burnett

Sven said > Yes (but you are free to use WebClient if you want). True, but I would much prefer to go with whatever the community to focused on. All I want is software that works :-) >SSL is not (yet) supported. Sorry. >BTW, It will be (very) hard to get Pharo+WebClient+SSL+MacOSX working. >There are workaround using stunnel. I haven't used stunnel before. I doesn't look too difficult to install, but when you say 'workaround' is it simply a case of install it, and then use it with Pharo. Or, do I have to make changes to Pharo to get it to take advantage of stunnel? Cheers Andy-- View this message in context: http://forum.world.st/WebClient-for-1-2-2-tp3485946p3488798.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 1, 2011

Re: [Pharo-users] Strange results from Zinc for the www.delicious.com domain

by Matt Kennedy

The URL in this case is responding with chunked encoding in the content, so the reader shouldn't need to be relying on the Content-Length header. When I was testing the delicious URL I noticed that they have an exceedingly short idle timeout before the server shuts down the connection. Removing the Connection: close header in the request was a workaround, putting the request into a keep alive mode which delicious supports by default, but their idle timeout is so short the request effectively works like a single connection if followup requests aren't immediately issued. On Sun, May 1, 2011 at 5:16 AM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 01 May 2011, at 04:28, arturus(a)gmail.com 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 > > > > -- Matt Kennedy

May 1, 2011

Re: [Pharo-users] WebClient for 1.2.2?

by Sven Van Caekenberghe

On 01 May 2011, at 01:21, Andy Burnett wrote: > Thanks guys, I was wondering about Zinc in relation to WebClient. So, just > to be clear, Zinc replaces WebClient as far as Pharo goes? Yes (but you are free to use WebClient if you want). > Second question. How do I create an SSL connection from the Zinc Client to a > server - that was one of the things that appealed to me about WebClient. > > Pharo 1.2.1 > OSX 10.6.6 SSL is not (yet) supported. Sorry. BTW, It will be (very) hard to get Pharo+WebClient+SSL+MacOSX working. There are workaround using stunnel. Sven

May 1, 2011

Re: [Pharo-users] Strange results from Zinc for the www.delicious.com domain

by Sven Van Caekenberghe

On 01 May 2011, at 04:28, arturus(a)gmail.com 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

May 1, 2011

Re: [Pharo-users] Strange results from Zinc for the www.delicious.com domain

by arturus＠gmail.com

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. On Apr 30, 2011 9:23pm, Andy Burnett <andy.burnett(a)knowinnovation.com> wrote: > I have just come across a very odd 'bug'? in Zinc. Evaluating the two > lines (below) will return the same result for the various domains I > tested, but not for Delicious. In their case, the HTTPClient returns what > I expected - ie the contents of the page. But, the Zinc client returns an > undefined object. Any thoughts on what is going on - user agent maybe?? > response := HTTPClient httpGet:'http://www.delicious.com'. > response2 := ZnHttpClient new url:'http://www.delicious.com'; get. > Cheers > Andy

May 1, 2011

Strange results from Zinc for the www.delicious.com domain

by Andy Burnett

I have just come across a very odd 'bug'? in Zinc. Evaluating the two lines (below) will return the same result for the various domains I tested, but not for Delicious. In their case, the HTTPClient returns what I expected - i.e. the contents of the page. But, the Zinc client returns an undefined object. Any thoughts on what is going on - user agent maybe?? response := HTTPClient httpGet:'http://www.delicious.com'. response2 := ZnHttpClient new url:'http://www.delicious.com'; get. Cheers Andy >

May 1, 2011