Ezequiel Garzon wrote :
> Hello! I know a lot is happening to httpd lately, so maybe this is not
> an issue anymore. I've noticed that a malformed HTTP request such as
>
> $ printf 'GET /file\r\n\r\n'| nc myhost 80
>
> doesn't just silently fail, but rather shuts down httpd. My
> /etc/httpd.conf is minimal:
>
> server default {listen on egress port 80}
>
> Has anybody else tried this?
>
> Thanks and cheers,
>
> Ezequiel
>
No crash in current, I get a "HTTP/1.0 500 Internal Server Error" response from
the server. However in the server logs I get different error messages as I
repeat the request:
Undefined error: 0 (500 Internal Server Error)
then:
Resource temporarily unavailable (500 Internal Server Error)
then:
No such file or directory (500 Internal Server Error)
That doesn't sound right.
-b
