Very Computer

My confusion has 3 parts:

1>
In the process of trying to debug why my Apache server often enters
a runaway CPU-burning loop upon some types of POST accesses to one of
our cgi-bin scripts, I have run into the following question?

in mod_cgi.c, cgi_handler(), argsbuffer is declared as
        char argsbuffer[HUGE_STRING_LEN] (which is #defined as 8192)

from what I can tell,this seems to be a limit on the maximum size of
a POST?  Can anyone shed any light on the subject?

2>
My problem specifically is that the server never seems to leave the
following loop from mod_cgi.c, lines 320-325, cgi_handler():

while (ramaining > 0) {
   int len_read, len_to_read = remaining;
   if (len_to_read > HUGE_STRING_LEN) len_to_read = HUGE_STRING_LEN;
   len_read = read_client_block (r, argsbuffer, len_to_read);
   if (len_to_read == 0) break;

Quote:}

3>
Finally, is_included is often a huge value like 8712, and since it is
declared immediately after argsbuffer, perhaps argsbuffer is overflowing
into it? Is this possible?

David Michaels

     remaining -= len_read;
     len_to_read -= len_read;

Quote:>    if (len_to_read == 0) break;
> }
> read_client_block() always seems to return the same block, forever, why?

> 3>
> Finally, is_included is often a huge value like 8712, and since it is
> declared immediately after argsbuffer, perhaps argsbuffer is overflowing
> into it? Is this possible?

--
  ,-/-  __      _  _         $Bill Luebkert
 (_/   /  )    // //       DBE Collectibles
  / ) /--<  o // //      http://www.westworld.com/~bill/