On 3/1/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> Update of /cvsroot/naviserver/naviserver/nsd
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv6669/nsd
>
> Modified Files:
> driver.c
> Log Message:
> Fixed error reporting during
> request parsing, now server returns 414/400 return codes and honors
> maxinput/maxheaders parameters. Test http-4.5 does not hang actually
> but with sndbuf/rcvbug set to so small values it takes very logn time to
> read the request, by putting Ns_Log in SockRead i was seeing reading by
> 64/192 bytes but the server was operational.
>
>
> Index: driver.c
> ===================================================================
> RCS file: /cvsroot/naviserver/naviserver/nsd/driver.c,v
> retrieving revision 1.43
> retrieving revision 1.44
> diff -C2 -d -r1.43 -r1.44
> *** driver.c 1 Mar 2006 04:30:59 -0000 1.43
> --- driver.c 1 Mar 2006 17:08:38 -0000 1.44
> ***************
> *** 1626,1629 ****
> --- 1647,1658 ----
> reqPtr->avail += n;
>
> + /*
> + * Check the hard limit for max uploaded content size
> + */
> +
> + if (reqPtr->avail > sockPtr->drvPtr->maxinput) {
> + return SOCK_ENTITYTOOLARGE;
> + }
> +
> return SockParse(sockPtr, spooler);
> }
> ***************
I think this is checking that the amount of data *already* received is
larger than maxinput, and if so, then rejecting. The idea is to not
read that much data in the first place.
I didn't look carefully so it may only be overshooting by the receive
buffer size or some such, but the same principle applies to the
following check for max headers. Here the headers have been
completely parsed into an Ns_Set structure, and *then* the size is
checked. Too late... :-(
> + /*
> + * Check for max number of headers
> + */
> +
> + if (Ns_SetSize(reqPtr->headers) > sockPtr->drvPtr->maxheaders) {
> + return SOCK_BADREQUEST;
> + }
> +
