Re: transparency - and DNS lookups

--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Henrik Nordstrom wrote:
>
> Oskar Pearson wrote:
> > I finally got sick of typing 'www.altavista.digital.com' in my
> > web browser, so I thought that I would get smart and add an entry
> > into '/etc/resolv.conf'.
> ...
> > The problem, however, is that I got a message back from the
> > cache saying that 'http://altavista/' didn't exist....
> ...
> > Which way do you guys think this should be handled?
>
> I'll actually consider this as a browser bug ;-) (not sending the known
> FQDN of the requested resource).

Trivial disagreement: Browsers just don't seem to...but the client
machine may have no domain configured in any case.

> The general way I think that "smart" lookups is to be handles is for the
> time being by a smart redirector returning redirects. This is only a
> variant of redirection and should be handled as such.
> As this kind of redirection is frequently requested functionality maybe
> we should add the functionality to core Squid without the need to mess
> with a redirector.

Are you suggesting something of the sort of thing like:
host_alias altavista www.altavista.digital.com
host_alias hell www.microsoft.com

etc?

> It is not very wise to let the resolver to solve this on it's own. The
> Host: header needs to be updated and it is feasible if the short hand
> hostname results in objects being is cached using the same key as
> requests using FQDN.
>
> /Henrik

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GAT d- s++: a C++++$ UL++++B+++S+++C++H++U++V+++$ P+++$ L+++ E-
W+++(--)$ N++ w++$>--- t+ 5++ X+() R+ tv b++++ DI+++ e- h-@ 
------END GEEK CODE BLOCK------
--MimeMultipartBoundary--