i agree with chuck's suggestion of using ethereal another tool which will help determine who or what is changing protocol is fiddler so you can examine the request and response http://www.fiddlertool.com/fiddler/
You might want to tracert and use fiddler to see which (intervening) node is changing the protocol also if you are able to publish to a public ip we can test it for you *grasping at straws (part 2)* HTH/ M- ----- Original Message ----- From: "Caldarale, Charles R" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Wednesday, December 05, 2007 1:32 PM Subject: RE: HTTP 1.1 Not Supported > From: Richard Sayre [mailto:[EMAIL PROTECTED] > Subject: Re: HTTP 1.1 Not Supported > > Here is the exact String exported from the packet: > > POST /test/sync/upload.jsp?username=test1 HTTP/1.1 > Content-Type: text/xml > Content-Length: 4005 > Connection: Keep-Alive > Expect: 100-continue > Host: 192.168.1.116 Look at it in hex and see if there's something funny in the above lines. Also check the line terminator for each and verify it's a CR/LF sequence. (Grasping at straws here.) - 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]
