Hello Johannes, I've completed the issue 1191 ( http://restlet.tigris.org/issues/show_bug.cgi?id=1191). As a workaround, you can use other server connectors (jetty or simple).
Best regards, Thierry Boileau Hi, > > I came across an interesting error > > If you just deploy a simple restlet and use the default Server > implementation which comes with restlet (Version 2.0.4) it works fine. > > Unless you specify the HTTP Header > > Connection:Close > > in this case the connection hangs and will never return anything. > > I tracked that down to an issue with the server connection. The output > stream seems to be in closing state, even though not response has been sent > yet. The code for writing the response will call canWrite on the stream > first and since it's in state closing will not output anything. > > The curl command line to reproduce this > curl -H "Connection: close" -v http://localhost:9999/firstSteps/hello > > By just deploying the sample restlet defined here > http://wiki.restlet.org/docs_2.0/13-restlet/275-restlet/311-restlet.html > > This is an issue with flash clients. They will generate an HTTP request > which has the connection header attribute set. > > Is that something that could be fixed? Or am I doing something wrong here? > > Thanks, > Johannes > > P.S. > Similar error on Stack Overflow > > http://stackoverflow.com/questions/4486572/problem-with-http-connection-close-header/4685230#4685230 > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2698048 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2698184
