The simple answer is that Jetty was expecting more bytes to be in the body of the POST than it actually got from the client using a persistent connection.
To look much further than this you should enable more verbose Jetty logging and you should be able to inspect the full request to see if there is a problem with the content-length in the request header or whether the client has simply closed the connection unexpectedly. Brett On Thu, 25 Jul 2002, Jules Gosnell wrote: > I'm forwarding you to jetty-discuss: > > Jules > > > Alex Loubyansky wrote: > > Hello guys, > > > > sometimes I meet the following warning: > > WARN [Jetty] WARNING: POST /<some-url/> HTTP/1.1 HttpException(400, > > Bad Request, Missing Content) > > > > Other times this same page is processed without it. All updates are > > done correctly in both cases. > > > > What does this warning mean? > > > > TIA ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
