Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: RE: Note On Setup
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Mon, 13 May 2002 23:36:39 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C6093@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Keen Wayne A Contr AFRL/MNGG" <keenwa AT eglin DOT af DOT mil>, <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4DDbDT18499

Not the incredibly obvious, more the someone is running a broken proxy,
or more likely an intercepting proxy, upstream of you. Take them out and
shoot them.

intercepting proxies are evil (outside of the reverse proxy aka
accelerator scenario), and broken ones even more so.

MSIE - quite rightly - does not send proxy cache control headers when it
doesn't know about the presence of a cache, so it assumes it is getting
a real response from the server when it requests a IMS, and until you go
refresh, older squids (and most other intercepting proxies) will give
you a cache hit instead. This breaks your browsing experience, because
of the idiotic network admin that is breaking the TCP end to end rules.

Rob

> -----Original Message-----
> From: Keen Wayne A Contr AFRL/MNGG [mailto:keenwa AT eglin DOT af DOT mil] 
> Sent: Monday, May 13, 2002 11:25 PM
> To: 'cygwin AT cygwin DOT com'
> Subject: Note On Setup
> 
> 
> Depending on the users connection, the following note may or 
> may not be helpful.
> 
> When I bring up the Cygwin page here at work, the page is, 
> most often, not current.  This is because, somewhere along 
> the way, somebody is caching an older version of the page. If 
> I try to grab setup from this older page, I run the risk it 
> seems of getting an older version of setup.  The way I have 
> found around this issue (which is NOT the fault of
> Cygnus) is that
> I will, pretty much automatically now, hit refresh several 
> times and wait to insure that I am getting the newest page.
> 
> Sorry if this fits under the category of incredibly obvious.
> 
> Wayne Keen
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/