#209 show-url-info fails via config.p.o

[Jürgen A. Erhard]

(I hate SF by now!... hope this isn't recorded, but
since it doesn't have a search feature...)

show-url-info and edit-actions-list fail when used via
config.privoxy.org
but work when I go via http://p.p

OS: Debian GNU/Linux "sid", package is 3.0.0-1

Browser: Mozilla (but I first encountered this on links
(ELinks 0.4pre5), though I dug into it on Mozilla)

Privoxy runs as a parent of squid. But it fails the
same way when Mozilla talks to it directly (proxy in
Mozilla configured). That's the only way I can use the
"p.p" shortcut anyway, since it doesn't resolve.

(BTW, why does config.p.o have *2* A records? Seems
quite a waste to me ;-)

[Jürgen A. Erhard]

Logged In: YES
user_id=10380

Forgot to mention: I get redirected to
http://www.privoxy.org/config/?f=default,
so it seems config.privoxy.org/edit-actions-list is replaced
with www.privoxy.org/config.

[Andreas Oesterhelt]

Logged In: YES
user_id=78811

Jrgen, thanks for your report.

You are reporting three issues:

1) "show-url-info and edit-actions-list fail when used via
config.privoxy.org", "Forgot to mention: I get redirected to
http://www.privoxy.org/config/?f=default,"

Reason: you are not using Privoxy for the domain
config.privoxy.org.
What you see is the result of a server-side redirect on the
(real) host
config.privoxy.org, where the request should never have been
forwarded, and where it would not have been forwarded, had
Privoxy been used.

Advice: Check that your browser's proxy settings really
match your
Privoxy set-up. Chack that privoxy.org (or .org!) are not
exempted from
proxying. Check Privoxy's log - you shouldn't see the
requests there.
If so, please post (attach) the log.

This is not a general problem of 3.0.0, so it must bei either
specific to the debian package or your setup. Since a bug
of that severity in the .deb would most probably have generated
more bug reports by now, chances are that something
about your setup causes this behaviour.

2.) When using Privoxy as a parent to squid, you can't
access "http://p.p/", only "http://config.privoxy.org".

Reason: The top-level domain "p" does not exist. Squid
notices and send an error document, instead of asking
its parent for the (invalid) URL.

Advice: Use the never_direct tag in squid_conf, which
instructs squid to blindly forward all queries to its parent.
Simple sample config for Privoxy and quid on the same host:

cache_peer localhost parent 8118 7 no-query
acl all src 0.0.0.0/0
never_direct allow all

3.) "why does config.p.o have *2* A records? Seems
quite a waste to me ;-)"

It's not, since config.privoxy.org aka www.privoxy.org aka
ijbswa.sf.net is hosted on SFs server farm.

HTH,
--Andreas

[Andreas Oesterhelt]

Logged In: YES
user_id=78811

If the redirected requests are in fact being logged by Privoxy,
please reopen this item.

If you have any other questions about the issues discussed
here, please open a new support request.