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,

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.

Here is the logfile:

[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
<http://www.xxx.com/xx/xxx/xxxxxxx/xxxxx?customerId=3Dxxx&xxx=3D23694546&xxx
=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)

And here is the VirtualHost in the Apache Conf:

<VirtualHost xxx.xxx.xxx.xxx>
ServerName xxx.xxxxxxxx.xxx <http://www.xxx/>
ErrorLog logs/xxxxxxx-error.log
CustomLog logs/xxxxxxx-access.log combined
<IfModule mod_proxy.c>
ProxyRequests Off
<ProxyMatch xxxx.xxxxxxx.xxx <http://www.xxxxxxx.xxx/> >
Order deny,allow
#Deny from all
Allow from all
</ProxyMatch>
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
</IfModule>
</VirtualHost>

The backend system is running with a Tomcatserver.

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.

Any hints??

Thank you very much for your help!!!

Cheeers,

Ueli



=2E

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1226" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2>Hello
guys,</FONT></SPAN></DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2>I am prox=
ying
several different URL's and directories with the mod_proxy.</FONT></SPAN></=
DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2>Everythin=
g runs just
fine except for one URL which comes back with a Bad Request.</FONT></SPAN><=
/DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2>Here is t=
he
logfile:</FONT></SPAN></DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2>[Thu Oct =
02 20:44:19
2003] [error] [client xxx.xxx.xxx.xxx] proxy: Error reading from remote ser=
ver
returned by /de/oks/Heineken/styles/style_yellow.css, referer: <A
href=3D"http://www.xxx.com/xx/xxx/xxxxxxx/xxxxx?customerId=3 Dxxx&xxx=3D=
23694546&xxx=3D23694546&tn=3D5000&tid=3D441726&a mp;re=3D2&l=
ang=3D1&ben=3D4528">http://www.xxx.com/xx/xxx/xxxxxxx/xx xxx?customerId=
=3Dxxx&xxx=3D23694546&xxx=3D23694546&tn=3D5000&a mp;tid=3D441726=
&re=3D2&lang=3D1&ben=3D4528</A><BR>[Thu
Oct 02 20:44:20 2003] [warn] proxy: bad HTTP/1.1 status line returned by
/xx/xxxx/xxxxxxx/img/0.gif (GET)</FONT></SPAN></DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2>And here =
is the
VirtualHost in the Apache Conf:</FONT></SPAN></DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2><Virtu=
alHost
xxx.xxx.xxx.xxx><BR>   ServerName xxx.xxxxxxxx<A
href=3D"http://www.xxx/">.xxx</A><BR>   ErrorLog
logs/xxxxxxx-error.log<BR>   CustomLog logs/xxxxxxx-access.log
combined<BR><IfModule mod_proxy.c><BR>   ProxyRequests
Off<BR><ProxyMatch xxxx<A
href=3D"http://www.xxxxxxx.xxx/">.xxxxxxx.xxx</A>><BR>   =
Order
deny,allow<BR>    #Deny from all<BR>    Allow=
from
all<BR></ProxyMatch><BR>   ProxyPass /xxx/ <A
href=3D"http://xxx.xxxxxx.xxx:8080/xxx/">http://xxx.xxxxxx.x xx:8080/xxx/</A=
><BR>  
ProxyPassReverse /xxx/ <A
href=3D"http://xxx.xxxxxx.xxx:8080/xxx/">http://xxx.xxxxxx.x xx:8080/xxx/</A=
><BR>  
ProxyPass / <A
href=3D"http://xxx.xxxxxx.xxx/">http://xxx.xxxxxx.xxx/</A><BR>  =

ProxyPassReverse / <A
href=3D"http://xxx.xxxxxx.xxx/">http://xxx.xxxxxx.xxx/</A><BR>   =
SetEnv
proxy-nokeepalive 1<BR>   SetEnv force-proxy-request-1.0
1<BR></IfModule><BR></VirtualHost></FONT></SPAN></DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2>The backe=
nd system
is running with a Tomcatserver.</FONT></SPAN></DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2>I have no=
idea,
where this bad status line is coming from, since I force the request protoc=
ol to
be in HTTP/1.0 and Tomcat will serve the Request in the same protocol
back.</FONT></SPAN></DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2>Any
hints??<BR></FONT></SPAN></DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2>Thank you=
very much
for your help!!!</DIV>
<DIV><BR></DIV></FONT></SPAN>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial
size=3D2>Cheeers,</FONT></SPAN></DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D058562211-03102003><FONT face=3DArial size=3D2> &nb=
sp; 
Ueli</DIV>
<DIV></FONT></SPAN> </DIV></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>.
</BODY></HTML>

------_=_NextPart_001_01C389A6.D4604EE4--
Ueli Kessler [ Fr, 03 Oktober 2003 14:06 ] [ ID #34754 ]

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
--
Graham Leggett [ Fr, 03 Oktober 2003 19:33 ] [ ID #34758 ]

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 [at] sharp.fm]
Sent: Freitag, 3. Oktober 2003 19:33
To: modproxy-dev [at] 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
> 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
--


=2E

------------=_1065511065-23413-38--
Ueli Kessler [ Di, 07 Oktober 2003 09:17 ] [ ID #34763 ]

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
--
Graham Leggett [ Di, 07 Oktober 2003 21:07 ] [ ID #34764 ]
Webserver » gmane.comp.apache.mod-proxy » Bad HTTP 1.1 request

Vorheriges Thema: Debug Flag
Nächstes Thema: proxy --> SSI