httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject Re: svn commit: r442758 - in /httpd/httpd/trunk/modules/generators: mod_cgi.c mod_cgid.c
Date Thu, 14 Sep 2006 00:25:46 GMT
Nick Kew wrote:
> 
> So we should log an error, not a success.  500 won't always be the ideal
> error, but I don't really see how we can do better within the current API.
> 
>> 500 implies that there could be an action to take to resolve a problem
>> (e.g., screwy filters bungled the return codes; screwy configuration;
>> out of memory; ???).  It doesn't apply when somebody bored with an
>> upload hit the Stop button.
> 
> So are you supporting RĂ¼diger's proposition?  I can accept that if it's
> the popular view.

At minimum report OK.  The request worked, the client fell away.  Admins go
crazy tracking down 500.

Maybe maybe an internal class of non-HTTP results such as 599 for
CLIENT_GONE_AWAY or something, but certainly not the conventional 500 codes
which represent broken activity on the server side.



Mime
View raw message