It looks like it's interpreting the whole '<soap>bla bla bla</soap>GET' as the method for the second request. Is there a two or three sets of '/r/n' (or just '/n' in Windows?) after the header in the first message; if three, perhaps it's interpreting the first message as a POST with no body?
Ron On Thu, Mar 26, 2009 at 3:52 AM, Andrea Martino <[email protected]> wrote: > > The output log contains the following: > > [Thu Mar 26 08:09:17 2009] [error] [client 192.168.1.50] File does not > exist: C:/Programmi/Apache Software Foundation/Apache2.2/htdocs/endpoint > [Thu Mar 26 08:09:17 2009] [error] [client 192.168.1.50] Invalid URI in > request <soap>bla bla bla</soap>GET /description HTTP/1.1 > > The access log: > > 192.168.1.50 - - [26/Mar/2009:08:09:17 +0100] "POST /endpoint HTTP/1.1" 404 > 206 > 192.168.1.50 - - [26/Mar/2009:08:09:17 +0100] "<soap>bla bla bla</soap>GET > /description HTTP/1.1" 400 226 > > The server is Apache/2.2.11 (Win32) PHP/5.2.9 (taken from the HTTP header > in the response) > > The 2 requests are sent together, very likely withing the same IP packet... > In Java I did: > > String request = "POST / .... <soap>xxx</soap>GET / HTTP ...."; > outputStream.write(request.getBytes()); > outputStream.flush(); > > > This behaviour really puzzles me... ;-) > > Thanks again > Andrea > > > > ----- Original Message ---- > From: Ruediger Pluem <[email protected]> > To: [email protected] > Sent: Thursday, March 26, 2009 8:28:55 AM > Subject: Re: HTTP pipelining in keep-alive requests > > On 26.03.2009 08:11, Andrea Martino wrote: > > Hi Rüdiger, > > I understand the request is not correct, but httpd answers anyway (at > least the version installed on my pc): > > What is the output of the error log and the access log? > Which version do you use? > What is the Timeout setting on your server? > Do you sent both request in one go or is there a pause time between both? > If yes how long? > > Regards > > Rüdiger > > > > -- Principal Software Engineer for Hire http://www.linkedin.com/in/ronaldparkjr
