nanog mailing list archives
Re: Digex transparent proxying
From: ken emery <ken () cnet com>
Date: Fri, 26 Jun 1998 21:28:30 -0700 (PDT)
On 27 Jun 1998, Michael Shields wrote:
In article <35935600.FF54EBFE () infowest com>, "Aaron D. Gifford" <agifford () infowest com> wrote:It might also be time for content providers of time-sensitive data on the web to redirect requests coming from Digex' proxy harvest machines to a web page that says something along the lines of "Digex has intercepted your web request and directed it through their web caching system. This impacts the time-sensitive data at this site. Hence you cannot access this site in this manner.
Any content provider savvy enough to put that up could just as easily put in the proper headers to tag their content as cacheable or uncacheable or cacheable until time X, and that would be better for *everyone* involved.
Except when listening to the "proper" headers has been turned off by the cache (which some of these caching products support or will support). bye, ken emery
Current thread:
- Digex transparent proxying Jon Lewis (Jun 25)
- Re: Digex transparent proxying Aaron D. Gifford (Jun 26)
- Re: Digex transparent proxying Nathan Stratton (Jun 26)
- Re: Digex transparent proxying Michael Shields (Jun 26)
- Re: Digex transparent proxying ken emery (Jun 26)
- Re: Digex transparent proxying Rich Sena (Jun 27)
- Re: Digex transparent proxying Paul Vixie (Jun 29)
- Re: Digex transparent proxying Karl Denninger (Jun 27)
- Re: Digex transparent proxying Rich Sena (Jun 27)
- Re: Digex transparent proxying Karl Denninger (Jun 27)
- Re: Digex transparent proxying Rich Sena (Jun 27)
- Re: Digex transparent proxying Karl Denninger (Jun 27)
- Re: Digex transparent proxying Rich Sena (Jun 27)
- Re: Digex transparent proxying andrew khoo (Jun 29)
- Re: Digex transparent proxying Rich Sena (Jun 27)
- Re: Digex transparent proxying Aaron D. Gifford (Jun 26)