Hello! here's some odd behaviour

Hi privoxy-users,

I'm new to the list and I was prompted to join by this thing which
looks a bit buggish to me.

Using v3.0.32 on Linux x64 (Debian Sid). Privoxy installation is all
defaults apart from enabling editing of actions files and restricting
access to the proxy to machines on my LAN.  This setup has worked for
me for years, and only went South when I added a custom actionsfile.

Here's my method to reproduce, with enable-edit-actions set to 1 in my
config:

* create a new empty actionsfile, eg "/etc/privoxy/foo.action"
* make sure foo.action has the same ownership and permissions as the
  other actionsfiles
* add an actionsfile directive for it in /etc/privoxy/config below
  the other actionsfile directives.
* restart Privoxy
* navigate to http://config.privoxy.org/show-status
* click on 'edit' next to /etc/privoxy/foo.action
* click on 'insert new section at top'

I get an error message saying that Privoxy can't write my custom
actionsfile. The message contains a spurious .action suffix but that's
because the template file supplies it and the code that interpolates the
template doesn't strip the suffix from the failing filename.

If I make an edit (any edit) in user.action, that edit succeeds.

I've tried moving foo.action before user.action in /etc/privoxy/config.
The files' order on the status page is altered but otherwise there's no
effect, foo.action is still the uneditable one.

I'm a bit stumped. My hope is that you all aren't.

Thanks,
Tim

--
Tim Magee