Re: transparency - and DNS lookups

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

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).

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.

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

--MimeMultipartBoundary--
Received on Tue Jul 29 2003 - 13:15:49 MDT