My apologies if this is veering off-topic again.
I've been experimenting since seeing the first post in the thread, and the
results are surprising. Note that I'm behind ADSL.
H D Moore <[EMAIL PROTECTED]> wrote:
>
> If you are hosting a web site wich serves non-public content from a
> public network, then yes, it a configuration issue.
First, I retrieve Slashdot's homepage from AltaVista, like this:
$ nc www.av.com 80
GET / HTTP/1.1
Host: www.slashdot.org
HTTP/1.1 200 OK
Transfer-Encoding: chunked
Date: Sun, 06 May 2001 09:04:04 GMT
Content-Type: text/html
Server: Apache/1.3.12 (Unix) mod_perl/1.24
Via: 1.1 BTDCCS08 (NetCache NetApp/5.0.1R2)
580
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML><HEAD><TITLE>Slashdot: News for nerds, stuff that matters</TITLE>
</HEAD>
... <rest deleted>
However, if I retrieve AltaVista via Slashdot, the request fails:
$ nc www.slashdot.org 80
GET / HTTP/1.1
Host: www.av.com
HTTP/1.1 302 Found
Date: Sun, 06 May 2001 09:17:04 GMT
Content-Length: 0
Connection: close
Server: Resin/1.2.1
Via: 1.1 BTDCCS08 (NetCache NetApp/5.0.1R2)
Location: http://uk.altavista.com/s?r=1
Of the handful of hosts I've experimented with, they including an Apache
server I run off-site. All return the "Via: " cache header with "NetCache
NetApp/5.0.1R2". So, two questions:
1. Are my requests being transparently redirected by my ISP to their caching
servers?
2. Why did the first example above succeed, but the second fail?
Thanks for your indulgence. :-)
--
Casper Boden-Cummins
S/MIME Cryptographic Signature
