Getting "Error reading header" messages in error_log

Getting "Error reading header" messages in error_log

am 16.12.2009 13:06:48 von Pravesh Rai

Hi,

We are getting either of the following error messages in error_log:

[error] [client ::1] client sent HTTP/1.1 request without hostname
(see RFC2616 section 14.23): /proxy/ssllogin, referer:

Or

[error] [client 127.0.0.1] request failed: error reading the headers,
referer:

& ultimately gets "Http 400 Page Cannot be Displayed" error page.

Further digging into the problem shows that even ap_rgetline_core()
[protocols.c] reads the HTTP header data wrongly. Some of the header
fields are either missing or overrun to other fields. Do anybody have
any idea on this ?

FYI, we are using Apache 2.2.6, PHP 5.2.9 & Openssl 0.9.8k for
building web-server.

Thanks & Regards,
Pravesh

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Fwd: Getting "Error reading header" messages in error_log

am 04.01.2010 12:28:16 von Pravesh Rai

Gentle reminder. Appreciate any clue for this question.

Thanks,
Pravesh

---------- Forwarded message ----------
From: Pravesh Rai
Date: Wed, Dec 16, 2009 at 5:36 PM
Subject: Getting "Error reading header" messages in error_log
To: users@httpd.apache.org


Hi,

We are getting either of the following error messages in error_log:

[error] [client ::1] client sent HTTP/1.1 request without hostname
(see RFC2616 section 14.23): /proxy/ssllogin, referer:

Or

[error] [client 127.0.0.1] request failed: error reading the headers,
referer:

& ultimately gets "Http 400 Page Cannot be Displayed" error page.

Further digging into the problem shows that even ap_rgetline_core()
[protocols.c] reads the HTTP header data wrongly. Some of the header
fields are either missing or overrun to other fields. Do anybody have
any idea on this ?

FYI, we are using Apache 2.2.6, PHP 5.2.9 & Openssl 0.9.8k for
building web-server.

Thanks & Regards,
Pravesh

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Getting "Error reading header" messages in

am 04.01.2010 16:29:08 von Krist van Besien

On Wed, Dec 16, 2009 at 1:06 PM, Pravesh Rai wrote:
> Hi,
>
> We are getting either of the following error messages in error_log:
>
> [error] [client ::1] client sent HTTP/1.1 request without hostname
> (see RFC2616 section 14.23): /proxy/ssllogin, referer:
>
> Or
>
> [error] [client 127.0.0.1] request failed: error reading the headers,
> referer:
>
> & ultimately gets "Http 400 Page Cannot be Displayed" error page.

That looks like a client that is not respecting the HTTP/1.1 protocol.

Krist


--
krist.vanbesien@gmail.com
krist@vanbesien.org
Bremgarten b. Bern, Switzerland
--
A: It reverses the normal flow of conversation.
Q: What's wrong with top-posting?
A: Top-posting.
Q: What's the biggest scourge on plain text email discussions?

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Getting "Error reading header" messages in

am 05.01.2010 06:41:40 von Pravesh Rai

Yes, you are right. But our concern is why some header fields are
missing during communication ?

Going through the debug messages indicates that, the communication
started very well & few intial pages are displayed normally, but after
some time, HTTP header information gets corrupted (either missing or
overrun to other fields).

FYI, we are getting this issue only on IA64 setup, whereas same set of
components (Apache, PHP & Openssl) works fine on x86 setup.

Regards,
Pravesh

On Mon, Jan 4, 2010 at 8:59 PM, Krist van Besien
wrote:
> On Wed, Dec 16, 2009 at 1:06 PM, Pravesh Rai wrot=
e:
>> Hi,
>>
>> We are getting either of the following error messages in error_log:
>>
>> [error] [client ::1] client sent HTTP/1.1 request without hostname
>> (see RFC2616 section 14.23): /proxy/ssllogin, referer:
>>
>> Or
>>
>> [error] [client 127.0.0.1] request failed: error reading the headers,
>> referer:
>>
>> & ultimately gets "Http 400 Page Cannot be Displayed" error page.
>
> That looks like a client that is not respecting the HTTP/1.1 protocol.
>
> Krist
>
>
> --
> krist.vanbesien@gmail.com
> krist@vanbesien.org
> Bremgarten b. Bern, Switzerland
> --
> A: It reverses the normal flow of conversation.
> Q: What's wrong with top-posting?
> A: Top-posting.
> Q: What's the biggest scourge on plain text email discussions?
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project=
..
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> =A0 " =A0 from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org