Jason King wrote:
I made the changes. still didn't help.
I'm a bit stumped then. Since this is how IE is responding to the content sent back by the web server, at this point I have to lean towards there being an issue of some sort between what Jetty's sending and how IE is reacting to it, but I really can't fathom why www would cause 413 errors and without www wouldn't.
I suggested turning off session variables as a troubleshooting method because of course then it shouldn't be settting any cookies which would shorten up the response ... was just curious if that mattered. Did you check live headers to see if at least you weren't getting all the cookie data coming across?
The only reference to Jetty and a 413 error is here: http://svn.codehaus.org/jetty/jetty/branches/jetty-6.1/VERSION.txt Search for 413 on that page, but here's the line: jetty-6.1.11 6 June 2008 + JETTY-336 413 error for full header buffer So it was a problem at one point--maybe it's rearing its head again? Here's the bug: http://jira.codehaus.org/browse/JETTY-336 And here's a comment you might try: "the call to setHeaderBufferSize can be done either in code or in jetty.xml. For each connector you are using, you need to add a line like: <Set name='headerBufferSize'>8096</Set>"The default is 4K (which even with the cookies you'd be under I'd think), and that still doesn't address why www would fail and the other would work, but maybe that's a bit more to go on.
-- Matthew Woodward [email protected] http://www.mattwoodward.com/blogPlease do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
smime.p7s
Description: S/MIME Cryptographic Signature
