#863 Disabling all filter files results in incorrect log messages

[Stefan Kurtz]

Hallo,
i want to use Privoxy as http/socks gateway (forward-socks) so the traffic should remain untouched. When i comment out all filter/action files in configuration file i get massive errors.
Error: Inconsistent configuration: tagging enabled, but no taggers available.
Error: Inconsistent configuration: header filtering enabled, but no matching filters available.

This is my configuration:

Actions Files:
None specified
Filter Files:
None specified
Trust File:
None specified

user-manual ./doc/user-manual/
confdir .
logdir .
logfile privoxy.log
debug 1
debug 1024
debug 4096
debug 8192
listen-address 127.0.0.1:8118
listen-address 192.168.1.6:8118
toggle 0
enable-remote-toggle 0
enable-remote-http-toggle 0
enable-edit-actions 0
enforce-blocks 0
buffer-limit 4096
enable-proxy-authentication-forwarding 0
forwarded-connect-retries 0
accept-intercepted-requests 1
allow-cgi-request-crunching 0
split-large-forms 0
keep-alive-timeout 5
tolerate-pipelining 1
socket-timeout 300
log-messages 1
log-buffer-size 1
log-max-lines 200
log-highlight-messages 1

What's wrong here?

[Fabian Keil]

Thanks for the report. Fixed in CVS.

As my previous message apparently didn't make it:

As a workaround you could keeping the default.filter file enabled and just comment out the action files. The memory fingerprint shouldn't matter, but you could further reduce it anyway by using a filter file with a single line like this:

FILTER: empty Empty filter to workaround Privoxy bug #3614835