Re: Compliance: reply with 400 (Bad Request) if request header is too big

On 08/30/2010 01:44 AM, Henrik Nordström wrote:
> The added comment applies to the whole 6xx class, not just 601.

We have only two 6xx constants. Are you saying HTTP_INVALID_HEADER (600)
is never sent to the client? I will adjust the comment if that is the case.

> Note: Not entirely sure we need these as internal http status codes in
> squid-3, but that's separate from this change.

Agreed on both counts.

Thank you,

Alex.

> sön 2010-08-29 klockan 14:57 -0600 skrev Alex Rousskov:
>> HTTP_INSUFFICIENT_STORAGE = 507, /**< RFC2518 section 10.6 */
>> HTTP_INVALID_HEADER = 600, /**< Squid header parsing
>> error */
>> - HTTP_HEADER_TOO_LARGE = 601 /* Header too large to
>> process */
>> + HTTP_HEADER_TOO_LARGE = 601 /**< Header too large to
>> process. Used
>> + internally only,
>> replying to client
>> + with HTTP_BAD_REQUEST
>> instead. */
Received on Mon Aug 30 2010 - 14:32:00 MDT