John D. Mitchell <jdmitchell <at> gmail.com> writes:
> Are you using the Simple HTTP connector in production? If so... Don't.
>
> Use Jetty instead.
Hi John,
Thanks for the suggestion. I switched over to Jetty. But while it doesn't barf
endless stack traces, it still borks occasionally on XHRs:
2008-01-28 13:48:09.838::WARN: handle failed
java.io.IOException: FULL head
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:276)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
2008-01-28 13:48:09.890::WARN: handle failed
java.io.IOException: FULL head
(same stack trace)
Jan 28, 2008 1:48:24 PM com.noelios.restlet.LogFilter afterHandle
This looks somewhat similar to a problem described here:
http://shorl.com/fraponurefyfu
...which essentially boils down to some strange confluence of
Jetty + Firefox + long cookie strings = bad times. However I've observed this
with IE 7 as well as Firefox 2.0.0.11.
Unfortunately I'm developing an intranet app and other developers felt the need
to hand out several ridiculously long cookies rooted at .domain.com so even
though I only ever need to use cookies at app.domain.com some users will come
through with these megacookies.
Does anyone have any advice on how to work around this? Or how to determine
whether the culprit is Firefox (sending malformed HTTP requests), the XHR
library, Jetty, or Restlet?
Thanks,
Mike
