On Sat, Apr 25, 2009 at 05:55:49PM +0200, Juliusz Chroboczek wrote:
>> Using Polipo I get a spurious 504 when using an unqualified host name
>
> Yes, that's normal. Polipo doesn't obey the domain search path in
> /etc/resolv.conf. For two reasons:
>
> 1. the /etc/resolv.conf of the host on which Polipo is running is not
> the right path to apply -- it's the client's search path that should
> be applied.
It's the case for me that polipo only listens to localhost, so it's
the same resolv.conf. Isn't this polipo's most likely deployment
method? It's marketed in the package description as a cache for
personal use.
It's particularly inconvenient for me, because
1) my "local" domain is 32 characters long -- a pain to type all the
time; but more importantly
2) the servers I'm trying to get to use vhosting, and they treat the
FQDN differently to the unqualified host name. In most cases,
this means I have to type in my username and password twice (once
for SSL, and once for the web app). In some cases, the FQDN
doesn't work at all, because nobody has bothered to set up a vhost
symlink for the FQDN.
Admittedly this is not polipo's fault, but I have absolutely no
chance of getting the servers setup fixed.
What this effectively means is that the least inconvenient way to
access internal hosts is to run a separate browsers for them, which
doesn't use polipo.
Would you be willing to add support for search domains, but turn it
off by default? Would you accept a patch that did so?
> 2. I'm opposed to using domain search paths, and I'm a stubborn bastard.
Well, I can't argue with that. I'd like to know WHY you're opposed to
them, if you have written an article on the subject.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
