Re: Wicket + Resin, Content-Length Header Issue

2009-03-10 Thread Seth Green
So... The only compression I know of is resin has a GZIP filter on it. But that means that everything is being GZIP'd, which is what I see in the headers for all requests (both to wicket /host/app/... and to non- wicket resources /host/css/...). I believe this (the wicket-generated wicket-aj

Re: Wicket + Resin, Content-Length Header Issue

2009-03-10 Thread Ryan Gravener
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 res

Wicket + Resin, Content-Length Header Issue

2009-03-10 Thread Seth Green
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 wh