httpd-test-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Bannert <>
Subject Re: Assert used in Flood and its triggering under Sun Solaris
Date Mon, 28 Apr 2003 14:56:48 GMT
This code for handling chunked-encoding is foreign to me,
but I'll try to see if I can help. It looks to me like the
assert() hits on chunked input parsing error*, so is it possible
that the socket read call didn't return enough data and the read
buffer simply didn't contain a CRLF yet?

Perhaps if you print out the contents of that buffer (when it
dumps core) and also send over the headers that your server
is responding with we might be able to track down the problem.

(* we really shouldn't be dumping cores on bad input, since
    we're ignoring malicious clients...)


On Monday, April 28, 2003, at 04:22  AM, Norman Tuttle wrote:

> Flood Developers on Solaris / in general:
> The flood website says that the majority of the developers for the 
> Flood
> project have developed it using Solaris and Linux. Therefore I am 
> curious
> to know why I might be seeing different behavior when running keepalive
> socket code on Solaris (than Win32 or Linux); specifically, it fails
> assert code found in the source file flood_socket_keepalive.c, thus
> aborting in the middle of a run with a core dump. This type of behavior
> does not occur with the code I have running on a Win32 system.
> Specifically, I want to know:
> (1) What is the purpose of the assert here, and why might it be failing
> specifically on a Solaris system?, and
> (2) What would be a more graceful way of reporting this error rather 
> than
> aborting the system with a core dump? I have an exception reporting
> mechanism in place, and just want to understand how the system should
> recover in this case. It seems that the code is highly coupled with
> notions of chunked encoding.

View raw message