On 2010-08-20 15.31, Thierry Boileau wrote: > I wonder if, in your case, the final server (not the proxy) is unable > to send a response, because of the closed socket error (on server > side). If so, the internal client connector will wait on the read > operation. As there is no timeout on this internal client connector > for the moment (it is planned to fix it for the 2.0 branch see > http://restlet.tigris.org/issues/show_bug.cgi?id=304), it will block. > This should not happen with the other client connectors.
That seems to be part of it. We found that a socket error lead to a branch of the code that never does unblock, and so the hang was unsurprising. We also just now found that the end server was doing Transfer encoding: chunked, which might cause problems. We'll try to remove that as well (no idea why it is doing so in the first place). >> BaseClientHelper code (because the catch code doesn't do unblock) > Do you refer to the BaseClientHelper#handle(Request, Response) > method? Yes. thanks, Rickard ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2649252
