Bug #1034
closed400-error when using fastcgi-php
Description
I'm running 1.5.0-r1605 and getting reports from my users that once in a while, some pages come up with a 400-error. When this happens, I get the following in my error.log file:
http_req.c.270: (trace) parsing failed ... (no error-msg)
My config is rather vanilla, though I spawn PHP externally and connect via IP/port (vs unix sockets or somesuch)
-- Toumal
Updated by Anonymous over 17 years ago
Version lighttpd-1.5.0-r1691
Yes...My error_log
http_req.c.270: (trace) parsing failed ... (no error-msg)
http_req.c.270: (trace) parsing failed ... (no error-msg)
http_req.c.270: (trace) parsing failed ... (no error-msg)
http_req.c.270: (trace) parsing failed ... (no error-msg)
http_req.c.270: (trace) parsing failed ... (no error-msg)
http_req.c.270: (trace) parsing failed ... (no error-msg)
How can I do?
Updated by Anonymous over 17 years ago
Update: The latest lighttpd-1.5.0-r1691 also exhibits this problem, exact same error message.
-- Toumal
Updated by Anonymous over 17 years ago
Yes,i also got is error message. Even in the svn version.
-- Dimu
Updated by gogo407 over 17 years ago
I also got this error message ,even i don't use php with lighttpd!
I use lighttpd-1.5.0 for our photo
Updated by Anonymous almost 17 years ago
We use lighttpd-1.5.0-r2025 to deliver static file (css, pictures, javascript) and we had the same problem here with a css file. The content of the file is delivered correctly but followed with a 400 bad request header, so the css is displayed empty (we seen this in firefox).
-- willy
Updated by gstrauss over 8 years ago
- Description updated (diff)
- Target version set to 1.5.0
Updated by gstrauss over 8 years ago
- Assignee deleted (
jan) - Missing in 1.5.x set to Yes
Also available in: Atom