Hi Eirik, Thanks for reporting this issue. I've checked in a fix for this in SVN trunk that sets the headers after the status and that ignores the "Content-Length" header when sending an error response.
Could you test it (from SVN trunk or from next snapshot) and let us know if it works? Rob, maybe you want to give it a try with GWT? Best regards, Jérôme Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : Eirik Bjørsnøs [mailto:[email protected]] Envoyé : mardi 6 janvier 2009 14:21 À : [email protected] Objet : Re: Redirect broken on Tomcat 5.0.x Cool. From what I understand the restlet engine will always add a Content-type: 0 header with no-entity responses, so that certainly sounds plausible if GWT hosted uses Tomcat 5.0.x. I started working on a patch but then I kind of put it aside when because of the long roundtrip and IDE trouble. It would be easier and more appealing for people like me to contribute if you guys had used Maven. Something to consider with your recent discussion around build systems on this list. Thanks, Eirik. On Tue, Jan 6, 2009 at 2:07 PM, Rob Heittman <[email protected]> wrote: > This is almost certainly the same as the known bug in GWT hosted mode > with no-entity responses. If the order of writing this header fixes > the problem transparently, it would be awesome to do it! > > On Mon, Jan 5, 2009 at 5:45 PM, Eirik Bjørsnøs <[email protected]> wrote: >> Setting the Content-Length to 0 on Tomcat 5.0.x effectively prevents >> any other headers or status coded being set because the response is >> considered to be committed according to the servlet spec. > > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1022201
