Closed GoogleCodeExporter closed 9 years ago
I do not believe that anything the server (itself not being a proxy) can cause a
proxy loop, in that the server can't choose your proxy for you.
That being understood, it's possible that the server response is somehow
offending
Polipo, and the error triggered by that. I think it's an erroneous error from
polipo, which it apparently has a history of.
If you would be so kind as to refer this to the polipo people, and if they can
specify what's offending them, and it's an out-of-spec performance by the
server, I
will certainly fix it.
Without some accurate feedback from polipo, I'm shooting in the dark.
Original comment by mcc...@gmail.com
on 3 Jul 2007 at 1:52
I upgraded to Polipo 1.0.1, and the problem went away. Apparently the issue
(whatever it was) has already been noticed and fixed by the Polipo developers.
I had assumed there was some sort of funny proxying involved in the Tcl Wiki
after
being reinstated, since it's the only site for which I have seen Polipo
misbehave.
Thank you for setting me straight about this.
I have sent an email about this problem to Juliusz Chroboczek, the primary
author of
Polipo.
Original comment by andrew.m.goth@gmail.com
on 3 Jul 2007 at 3:22
It may *well* be that there's some Wub deviation from the standard which causes
polipo to get offended. If you do happen to find out what that is, I'd be
interested
to learn it, so that I can fix it.
Original comment by mcc...@gmail.com
on 3 Jul 2007 at 2:32
[deleted comment]
[deleted comment]
(for some reason I seem to be having problems adding comments)
The author of Polipo writes:
> Accessing any page in the Tcl Wiki (http://wiki.tcl.tk/) results in an
> erroneous 504 when using Polipo 0.9.9. Upgrading to 1.0.1 fixes the problem.
No, it doesn't, it just works around it. You can still reproduce the
issue with 1.0.1 if you set
disableVia: false
in Polipo's config file.
The Wiki code is broken. For some strange reason, it is echoing the
client's Via header in the reply. This breaks Polipo.
Juliusz
Original comment by andrew.m.goth@gmail.com
on 3 Jul 2007 at 4:25
Original issue reported on code.google.com by
andrew.m.goth@gmail.com
on 3 Jul 2007 at 1:07