Hello Guido, I'm not sure to fully understand your configuration. Let me reformulate what i understand. You are using the current snapshot of Restlet 2.1. There is a first application served by the internal HTTP connector. It also hosts a set of GWT pages. There is another application, also served by the internal HTTP connector which also hosts a set of GWT pages. The first application sends requests to the second one using the client extension based on the Apache httpclient libray. Am I right? I've tried this configuration, and it works well for me.
Best regards, Thierry Boileau Hi, > > when using a ClientResource inside GWT-JSE 2.1snap to request a POST from > another GWT-JSE 2.1snap server using Apache HttpClient the request times > out > whenever the POST is the first call to the remote server. > > It seems that the underlying connection is not established. As soon as a > HEAD or GET is executed in parallel (eg. by requesting some other resource) > the connection becomes available and the hanging POST call is completed > correctly. > > As a workaround for now I always add a HEAD just before the POST. > > Guido Schmidt. > -- > View this message in context: > http://restlet-discuss.1400322.n2.nabble.com/If-POST-is-first-method-connection-is-not-established-tp5921068p5921068.html > Sent from the Restlet Discuss mailing list archive at Nabble.com. > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2698015 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2698190
