RE: [squid-users] Re: WARNING: unparseable HTTP header field {:: }

On 2013-11-13 07:45, Jenny Lee wrote:
> They generate huge log files. We turn them off. Here it a patch for
> 3.3.10 if you need to suppress them.
>
> Some of the cache log options should have config entries as they
> generate clutter and hide more important issues. We remove the
> following as well:
>
> * "Username ACLs are not reliable here"
> * "ACL is used but there is no HTTP request" (generates very huge
> files when peer is dead)
> * "Failed to select source for" (Fixed in 3.3.10)
> * Host Header Forgery crap
>
> J
>
> --- HttpHeader.cc.orig 2013-11-08 11:33:47.965826408
> +++ HttpHeader.cc 2013-11-08 11:34:56.248823857
> @@ -620,7 +620,7 @@ HttpHeader::parse(const char *header_sta
>
> if (field_start == field_end) {
> if (field_ptr < header_end) {
> - debugs(55, DBG_IMPORTANT, "WARNING: unparseable HTTP
> header field near {" <<
> + debugs(55, 3, "WARNING: unparseable HTTP header field
> near {" <<
> getStringPrefix(field_start, header_end) <<
> "}");
> goto reset;
> }
> @@ -629,7 +629,7 @@ HttpHeader::parse(const char *header_sta
> }
>
> if ((e = HttpHeaderEntry::parse(field_start, field_end)) ==
> NULL) {
> - debugs(55, DBG_IMPORTANT, "WARNING: unparseable HTTP
> header field {" <<
> + debugs(55, 3, "WARNING: unparseable HTTP header field {"
> <<
> getStringPrefix(field_start, field_end) << "}");
> debugs(55, Config.onoff.relaxed_header_parser <= 0 ? 1 :
> 2,
> " in {" << getStringPrefix(header_start,
> header_end) << "}");
>

Thats the general idea. Although replacing the fixed level with
(Config.onoff.relaxed_header_parser <= 0 ? DBG_IMPORTANT : 2) would be
better and leave is configurable with the relaxed_header_parser direcive
(can be set to warn / on / off - default is on which is quiet).
  I'm applying that change to 3.HEAD right now for these and a few nearly
warnings with the same noise problem.

Amos
Received on Tue Nov 12 2013 - 22:22:40 MST