I searched Resin Accept-Encoding and looks like I found your papernapkin paste: http://www.papernapkin.org/pastebin/view/4871/
The response header had: Transfer-Encoding: chunked, which would mean that the server is doing on the fly compression and no content-length will ever be sent. Perhaps resin is failing to compress the file. Ryan Gravener http://ryangravener.com/flex | http://twitter.com/ryangravener On Tue, Mar 10, 2009 at 9:51 AM, Seth Green <[email protected]> wrote: > I'm running wicket (1.2.6) on both Jetty and Resin (3.0.25). > > Everything appears to work correctly on Jetty. However, on Resin, when > requesting the wicket-ajax.js file, it is sent back without a content-length > header and is therefore unreadable by the browser. It appears this only > happens when using compression (gzip, in this case). Requesting the file > without compression, using cURL, returns the correct headers. > > I am not using a proxy, this occurs when directly accessing Resin. > > Has anyone every experienced this behavior, and/or can provide some > insight? > > Thanks. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
