Thanks for this Gustaf,
I'm rolling up my sleeves, and have just put on my new C hat (never worn
before). Let's see how I get on
Brian
From: AOLserver Discussion [AOLSERVER@LISTSERV.AOL.COM] On Behalf Of Gustaf
Neumann [neum...@wu-wien.ac.at]
Sent:
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
Jim Davidson wrote:
I think today, in 2011, some of the flexibility we imagined back in
1995 isn't really so needed. This includes general purpose logging
plugins and network drivers when there really is just the common log
format, ordinary and SSL sockets. More in the core for the base HTTP
