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

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Sun, 29 Aug 2010 22:03:54 +0000

On Sun, 29 Aug 2010 14:57:08 -0600, Alex Rousskov
<rousskov_at_measurement-factory.com> wrote:
> Compliance: reply with 400 (Bad Request) if request header is too big.
>
> Reply with a standard 400 (Bad Request) instead of 601 (Unknown) status
> in case of an ERR_TOO_BIG error. HTTP does not have a dedicated code for

> the too-big header error. There is 414 (Request-URI Too Long), but Squid

> does not distinguish too-large headers from too-large URIs.
>
> Co-Advisor test case: test_case/rfc2616/longUri-65536

+1.

NP: Followup to the unit-test and HttpParser work I'm doing now on the
request-line parser leads to sending those 414 and other closely related
errors instead of the generic one.

Amos
Received on Sun Aug 29 2010 - 22:03:58 MDT

This archive was generated by hypermail 2.2.0 : Mon Aug 30 2010 - 12:00:05 MDT