Your message dated Sun, 30 Jul 2006 14:15:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#315350: privoxy: doesn't go there anyway
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: privoxy
Version: 3.0.3-4
Severity: normal
to reproduce (maybe) with privoxy running and using firefox, load a page with
google ads, with links like
http://pagead2.googlesyndication.com/pagead/adclick?sa=L&adurl=http://www.google.com&ai=
then when you get a page saying
BLOCKED
This is Privoxy 3.0.3 ...
Request for blocked URL
....
click on go there anyway.
the resulting url should be the same as above but with PRIVOXY-FORCE
after the host. privoxy should not do any filtering, but does for me.
ask away.
thanks.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.11--from-2.6.9-proc-config-and-menuconfig
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages privoxy depends on:
ii adduser 3.63 Add and remove users and groups
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libpcre3 4.5-1.2 Perl 5 Compatible Regular Expressi
ii logrotate 3.7-5 Log rotation utility
-- debconf-show failed
--- End Message ---
--- Begin Message ---
On Sat, 29 Jul 2006, t takahashi wrote:
> it's a year later, and it works now. i didn't notice that it was
> fixed because i rarely go there anyway. ok to close.
Okay, so I close this bug report now.
> a far bigger problem i have is that i get 404 pages 9 times out of 10.
> but i'm not sure it's a privoxy problem.
I'll apply a patch to the next Debian release which retries a DNS
lookup 10 times before giving up. Maybe this solves your problem,
which is reported in Bug#335660 in a similar way...
Ciao
Roland
--- End Message ---
