From: SourceForge.net <no...@so...> - 2009-05-27 14:29:20
|
Support Requests item #2797228, was opened at 2009-05-27 07:53 Message generated for change (Comment added) made by fabiankeil You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=2797228&group_id=11118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: filters Group: 3.0.x >Status: Pending Priority: 5 Private: No Submitted By: Alexey Subbotin (avs234) >Assigned to: Fabian Keil (fabiankeil) Summary: Client header filters won't work Initial Comment: I'm using 3.0.12-stable (Linux 64-bit, compiled from sources). Adding a CLIENT-HEADER-FILTER doesn't work for me. E.g., the headers are not rewritten when I add a filter like CLIENT-HEADER-FILTER: myfilter s/^(Accept-Charset:).*/$1 utf-8whatever/ together with the relevant action (no matter which specific field I use instead of Accept-Charset) { +filter{myfilter} } / The built-in Privoxy action lookup web-page says that the rule matches, however... I wonder what I'm doing wrong??? ---------------------------------------------------------------------- >Comment By: Fabian Keil (fabiankeil) Date: 2009-05-27 14:29 Message: You defined a client-header filter, but told Privoxy to apply a content filter with the same name. The action your looking for is: http://www.privoxy.org/user-manual/actions-file.html#CLIENT-HEADER-FILTER ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=2797228&group_id=11118 |