Hello! Has this design limitation been solved in newer squid versions? Ciao, Gerhard -- http://www.wiesinger.com/ ---------- Forwarded message ---------- Date: Wed, 26 Mar 2003 07:48:29 +0100 (CET) From: Gerhard Wiesinger <lists@xxxxxxxxxxxxx> To: squid-users@xxxxxxxxxxxxxxx Subject: header_access design problem? Hello! I'm trying to get the header_access feature to work (squid 2.5.STABLE2). It works well except the following: 1.) header_access works for Request headers well, but Response headers are cutted to!!! 2.) Adding an currently unknown header (e.g. Depth for WebDAV) requires source compilation and modification. Also adding other new headers should be much more easier. (e.g. config). Maybe there should be a warning message, but filtering should be done correctly. If it is not done the following warning occours: 2003/03/26 07:45:38| squid.conf line 2851: header_access Depth allow all 2003/03/26 07:45:38| parse_http_header_access: unknown header name Depth. HttpHeader.c: --- HttpHeader.c.orig Tue Mar 25 17:25:03 2003 +++ HttpHeader.c Tue Mar 25 17:25:44 2003 @@ -126,6 +126,7 @@ {"X-Request-URI", HDR_X_REQUEST_URI, ftStr}, {"X-Squid-Error", HDR_X_SQUID_ERROR, ftStr}, {"Negotiate", HDR_NEGOTIATE, ftStr}, + {"Depth", HDR_DEPTH, ftStr}, #if X_ACCELERATOR_VARY {"X-Accelerator-Vary", HDR_X_ACCELERATOR_VARY, ftStr}, #endif --- enums.h.orig Tue Mar 25 17:22:46 2003 +++ enums.h Tue Mar 25 17:24:37 2003 @@ -236,6 +236,7 @@ HDR_X_REQUEST_URI, /* appended if ADD_X_REQUEST_URI is #defined */ HDR_X_SQUID_ERROR, HDR_NEGOTIATE, + HDR_DEPTH, #if X_ACCELERATOR_VARY HDR_X_ACCELERATOR_VARY, #endif Thank you for the answer. Ciao, Gerhard
