| Because the cached data for non-transparent use is hashed and stored
|under the URL based on its FQDN, e.g.
|
|squid.nlanr.net/Squid/FAQ/index.html
|
|and with transparent use the FQDN is not available, so it'll be stored
|under the numeric IP, or the equivalent of (e.g.)
|
|192.172.226.146/Squid/FAQ/index.html
|
|the two will be stored as completely different files. So there ends up
|being no benefit at all of sharing the server, right?
|
| That's led me to wonder - would it work out to add code to Squid to
|store the non-transparent cached files under the numeric IP (which it
|has to look up anyway, to query the server)? This would be less
|efficient in space in cases where a given FQDN is load-balanced across
|several replicated web servers with distinct numeric IP addresses, but
|still more efficient than storing all of those *plus* the FQDN. Where
|there's one IP address for a given FQDN, it's a significant win.
|
| Is anyone working on this as an option/hack? If code were to be
|written for this as an option with an enable-flag, would the Squid
|developers be willing to mainstream it?
Not quite right we have here 100G proxy doing both regular and
transparent requests with "httpd_accel_uses_host_header" enabled - it
stores all fetched objects by URL when supplied (my stats is 97% of all
request to transparent proxy).
Leonid Igolnik aka LiM
Received on Thu Jul 01 1999 - 01:20:07 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:47:15 MST