My setup is intercepting with iptables. Works well. But here is a problem with URL rewriting
CLIENT-HEADER-FILTER: test
s@qwerty@asdfg@
{ +client-header-filter{test} }
192.0.2.1
Next request fails with
Privoxy ran out of memory while processing your request.
Please contact your proxy administrator, or try again later
curl "http://192.0.2.1/qwerty" - FAILS
2015-08-26 15:29:45.070 7796c530 Re-Filter: filtering 'GET /qwerty HTTP/1.1' (size 20) with 'test' ...
2015-08-26 15:29:45.074 7796c530 Re-Filter: ... produced 1 hits (new size 19).
2015-08-26 15:29:45.074 7796c530 Re-Filter: filtering 'User-Agent: curl/7.32.0' (size 23) with 'test' ...
2015-08-26 15:29:45.074 7796c530 Re-Filter: ... produced 0 hits (new size 23).
2015-08-26 15:29:45.075 7796c530 Re-Filter: filtering 'Host: 192.0.2.1' (size 15) with 'test' ...
2015-08-26 15:29:45.075 7796c530 Re-Filter: ... produced 0 hits (new size 15).
2015-08-26 15:29:45.075 7796c530 Re-Filter: filtering 'Accept: /' (size 11) with 'test' ...
2015-08-26 15:29:45.075 7796c530 Re-Filter: ... produced 0 hits (new size 11).
2015-08-26 15:29:45.076 7796c530 Request: /asdfg
If rewriting is not involved, everything is perfect (notice difference in last lines of output)
curl "http://192.0.2.1/qwert" - WORKS
2015-08-26 15:29:55.325 77b6c530 Re-Filter: filtering 'GET /qwert HTTP/1.1' (size 19) with 'test' ...
2015-08-26 15:29:55.326 77b6c530 Re-Filter: ... produced 0 hits (new size 19).
2015-08-26 15:29:55.326 77b6c530 Re-Filter: filtering 'User-Agent: curl/7.32.0' (size 23) with 'test' ...
2015-08-26 15:29:55.326 77b6c530 Re-Filter: ... produced 0 hits (new size 23).
2015-08-26 15:29:55.326 77b6c530 Re-Filter: filtering 'Host: 192.0.2.1' (size 15) with 'test' ...
2015-08-26 15:29:55.327 77b6c530 Re-Filter: ... produced 0 hits (new size 15).
2015-08-26 15:29:55.327 77b6c530 Re-Filter: filtering 'Accept: /' (size 11) with 'test' ...
2015-08-26 15:29:55.327 77b6c530 Re-Filter: ... produced 0 hits (new size 11).
2015-08-26 15:29:55.327 77b6c530 Request: 192.0.2.1/qwert
Thanks for the report and the detailed problem description.
This is a bug and I'll look into fixing this.
This should be fixed in CVS now.
The recent 3.0.24 release includes the fix.