A thought for an alternate way to handle this - if the content-length is
too large, the just don't read the content, but set an error flag on the
conn. That way, an adventurous system could return a custom error page,
or even handle reading the content through custom code. I think this
could also allow handling of uploaded files larger than 2G as someone
else was having.
The default handling by returning a 413 error could be implemented as a
pre-queue filter, which would still handle the error without needing a
conn thread.
If anyone's messing around in there, this might be a good time to also
think about how to handle http/1.1's 'Expect: 100-continue', which
should be most beneficial for large entity bodies anyway.
-J
Dossy Shiobara wrote:
Yes, on E_CRANGE, the driver thread should return HTTP 413 Request too
large, IMHO. And, we should be able to configure a custom response for
status code 413 ...
Patches welcome ;)
On 6/23/11 11:28 AM, Fenton, Brian wrote:
I'm using OpenACS hence the TCL. I just want to let the user know that
their file is over the size limit. Could we, in driver.c instead of
closing the connection socket, return a custom template (like Apache
does) ?
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<lists...@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
