-
You could still divide your replacement text across multiple filter lines and only let the last filter line remove the matched text.
2009-11-10 16:49:35 UTC in Privoxy
-
Thanks for reporting the problem, but without more information there's nothing we can do about it.
A logfile that shows the problem would be a start.
2009-11-10 16:25:53 UTC in Privoxy
-
fabiankeil committed patchset 4466 of module current to the Privoxy CVS repository, changing 2 files.
2009-11-10 16:20:18 UTC in Privoxy
-
fabiankeil committed patchset 4465 of module current to the Privoxy CVS repository, changing 1 files.
2009-11-10 16:19:38 UTC in Privoxy
-
You're welcome.
We keep all the reports around and don't have direct access to the database anyway, so you should be able to reopen the request if necessary.
2009-11-09 19:02:06 UTC in Privoxy
-
I think the URL to the bug report should be a link.
The title of the Firefox bug report should probably be in tags.
"+handle-as-empty-document" should probably be either a link or in tags. Looks like p-config.sgml isn't consistent there.
Other than that the patch looks fine to me and if necessary, we can always improve it after it has been committed.
I most likely won't...
2009-11-09 18:54:20 UTC in Privoxy
-
Thanks for the report.
I think the script you are looking for is:
http://ijbswa.cvs.sourceforge.net/viewvc/*checkout*/ijbswa/winsetup/privoxy_winthreads.nsi
Quote:
; save files the user might have changed
; config.txt match-all.action trust.txt user.action user.filter
; NOTE: rename fails if the destination file already exists
;
[...]...
2009-11-09 18:06:24 UTC in Privoxy
-
Looks great.
If the flags are sorted by bit order, I can live with that, too.
I'd prefer the option to be off by default, but it's not that important to me.
It needs to be documented, no matter if it's on or off by default, though.
2009-11-08 19:37:20 UTC in Privoxy
-
Please have a look at Privoxy's debug settings at:
http://www.privoxy.org/user-manual/config.html#DEBUG
If you configure a logfile and enable everything but "debug 64" and "debug 16", you should get a pretty good idea of what kind of headers Privoxy is receiving and what it does with them.
2009-11-08 18:45:41 UTC in Privoxy
-
Looks good, there are a couple of minor issues though:
In block_url(), the comment text in the if block should start below the "/*" line and the else block should use curly braces.
I think the rsp->status line should be either "200 OK. Request blocked by Privoxy" or "200 Request blocked by Privoxy". Firefox should be happy either way, but you may want to verify this.
In load_config()...
2009-11-08 13:36:50 UTC in Privoxy
