Ok so I've caputured a large amount of data and I always see something like
POST ?data=blah... its never blank but its not going to a specific webpage or anything, just to the host itself. On Wed, Feb 13, 2008 at 5:50 PM, Len Popp <[EMAIL PROTECTED]> wrote: > Chuck is referring to the part of the HTTP request that specifies > which web page to fetch. If that piece is missing, it could cause the > problem you're seeing. > > Examine your traffic log and find one of the problem requests. The > first line of the HTTP request (after the TCP/IP headers) should look > something like this: > GET /index.html HTTP/1.1 > If instead you see this: > GET HTTP/1.1 > that's an invalid request. > > It seems that this type of invalid request can cause Tomcat to choke. > It should return an HTTP error 400 to the client, indicating the > request is bogus. > -- > Len > > > On Feb 13, 2008 6:15 PM, Steven <[EMAIL PROTECTED]> wrote: > > Hi Chuck, > > > > Ok so I got wireshark all setup and was able to capture the request that > are > > generating empty reponses. But looking at the traffic log, im not sure > what > > is different between a request that produces the error and on ethat does > > not. You mentioned the URI is null. Sorry, but im still not clear on > what > > you mean when you say that. Is hte URI that is used to send the request > to > > my tomcat instance cleared out somehow? The strange thing is sometimes > the > > error occurs and sometiems it doesn't. I really do appreciate your help > on > > this! > > > > Thanks! > > Steven > > > > On Feb 12, 2008 2:54 PM, Caldarale, Charles R < > [EMAIL PROTECTED]> > > wrote: > > > > > > > > From: Steven [mailto:[EMAIL PROTECTED] > > > > Subject: Re: Sporadic Errors in catalina log > > > > > > > > When you say empty URI, you mean after the root address? because > its > > > > getting to my tomcat server so it must at least have that. > > > > > > Not necessarily; what curl puts in the payload may or may not include > > > the URL you give it, depending on protocol and other options. Taking > a > > > Wireshark trace would let you see what's really being sent. > > > > > > - Chuck > > > > > > > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE > PROPRIETARY > > > MATERIAL and is thus for use only by the intended recipient. If you > > > received this in error, please contact the sender and delete the > e-mail > > > and its attachments from all computers. > > > > > > --------------------------------------------------------------------- > > > To start a new topic, e-mail: users@tomcat.apache.org > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
