Bad HTTP 1.1 request

This is a multi-part message in MIME format...

------_=_NextPart_001_01C389A6.D4604EE4
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello guys,
=20
I am proxying several different URL's and directories with the
mod_proxy.
Everything runs just fine except for one URL which comes back with a Bad
Request.
=20
Here is the logfile:
=20
[Thu Oct 02 20:44:19 2003] [error] [client xxx.xxx.xxx.xxx] proxy: Error
reading from remote server returned by
/de/oks/Heineken/styles/style_yellow.css, referer:
http://www.xxx.com/xx/xxx/xxxxxxx/xxxxx?customerId=3Dxxx
=3D23694546&tn=3D5000&tid=3D441726&re=3D2&lang=3D1&ben=3D452 8>
&xxx=3D23694546&xxx=3D23694546&tn=3D5000&tid=3D441726&re=3D2 &lang=3D1&ben=
=3D4528
[Thu Oct 02 20:44:20 2003] [warn] proxy: bad HTTP/1.1 status line
returned by /xx/xxxx/xxxxxxx/img/0.gif (GET)
=20
And here is the VirtualHost in the Apache Conf:
=20

ServerName xxx.xxxxxxxx.xxx =20
ErrorLog logs/xxxxxxx-error.log
CustomLog logs/xxxxxxx-access.log combined

ProxyRequests Off
>
Order deny,allow
#Deny from all
Allow from all

ProxyPass /xxx/ http://xxx.xxxxxx.xxx:8080/xxx/
ProxyPassReverse /xxx/ http://xxx.xxxxxx.xxx:8080/xxx/
ProxyPass / http://xxx.xxxxxx.xxx/
ProxyPassReverse / http://xxx.xxxxxx.xxx/
SetEnv proxy-nokeepalive 1
SetEnv force-proxy-request-1.0 1


=20
The backend system is running with a Tomcatserver.
=20
I have no idea, where this bad status line is coming from, since I force
the request protocol to be in HTTP/1.0 and Tomcat will serve the Request
in the same protocol back.
=20
Any hints??

Thank you very much for your help!!!

Cheeers,
=20
Ueli
=20
=20



------_=_NextPart_001_01C389A6.D4604EE4
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Re: Bad HTTP 1.1 request

Ueli Kessler wrote:

> I have no idea, where this bad status line is coming from, since I force
> the request protocol to be in HTTP/1.0 and Tomcat will serve the Request
> in the same protocol back.

The best thing to do is sniff the connection to determine what the
status line is exactly, this way you can see whether there is something
wrong with the status line or not.

One tool that can do this is tcpflow, there are others.

Regards,
Graham
--

RE: Bad HTTP 1.1 request

This is a multi-part message in MIME format...

------------=_1065511065-23413-38
content-class: urn:content-classes:message
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


Hi Graham,
I've never dealt with status lines.
What are status lines exactly and what are they needed for?

Thank you very much for a quick update.

Kind Regards,

-Ueli

-----Original Message-----
From: Graham Leggett [mailto:minfrin@sharp.fm]=20
Sent: Freitag, 3. Oktober 2003 19:33
To: modproxy-dev@apache.org
Subject: Re: Bad HTTP 1.1 request


Ueli Kessler wrote:

> I have no idea, where this bad status line is coming from, since I=20
> force
> the request protocol to be in HTTP/1.0 and Tomcat will serve the
Request=20
> in the same protocol back.

The best thing to do is sniff the connection to determine what the=20
status line is exactly, this way you can see whether there is something=20
wrong with the status line or not.

One tool that can do this is tcpflow, there are others.

Regards,
Graham
--




------------=_1065511065-23413-38--

Re: Bad HTTP 1.1 request

Ueli Kessler wrote:

> I've never dealt with status lines.
> What are status lines exactly and what are they needed for?

The status line describes the response the webserver returns to the
browser when it receives a request. One of the more common status lines
is "200 OK", another one is "304 Not Modified". If the remote webserver
does not return a status line, or if the status line is corrupt, the
proxy will give an error.

Regards,
Graham
--