Transparent proxying using URL rather than IP addrs

Hello,

I tested that patch of yours for 1.1.11 (which patched cleanly on 1.1.14) -
it's happily running on one of my subsidiary caches. No visible problems as
yet (other than the 2.0.30 kernel's inability to redir to anything other
than the original port).

 Elfredy Cadapan
  Computer Science Instructor and Professional Nerd
  Institute of Computer Science, UP at Los Banos
  Home page : http://www.uplb.edu.ph/~evc/

----------------------------
Date: 21 Sep 1997 04:39:59 +0200
From: miquels@cistron.nl (Miquel van Smoorenburg)
To: squid-users@nlanr.net
Subject: Re: Cisco Cache Director (Was RE: Does Squid beat the rest? )
Message-ID: <6021dv$k60$1@defiant.cistron.nl>

In article <Pine.LNX.3.95.970920184153.11052A-100000@nightshade.z.ml.org>,
Gregory Maxwell <nullc@nightshade.z.ml.org> wrote:
>
>You can do this with Linux and Squid.. It's called transparent proxing,
>unfortuantly there is a rather BIG problem with this, The cache only sees
>the IP and not the URL, so it severly reduces hit rate.. Some people on
>this list use Transparent proxying, they can tell you how it works..

But, the code is _in there_ to proxy based on URL. Because the URL is passed
in the Host: header. It's just not turned on for transparent proxying,
but it is for the accelerator code.

A while ago I posted a patch like the following for squid 1.11 but I never
actually tested it myself (in the great Linus Torvalds tradition :)) however
it did compile. On inspection later I found out it probably didn't work.

-- 
| Miquel van Smoorenburg |                                                    |
| miquels@cistron.nl     | Owners of digital watches, your days are numbered. |
|     PGP fingerprint: FE 66 52 4F CD 59 A5 36  7F 39 8B 20 F1 D6 74 02       |