Re: expiring content on win2k and IIS5 servers
by "Kathy Evans" <kje(at)vendetta.co.uk>
|
Date: |
Mon, 20 Nov 2000 18:59:36 -0000 |
To: |
"Phil Babcock" <pbabcock(at)bgsgroup.com>, "Hwg-Servers (E-mail)" <hwg-servers(at)hwg.org> |
References: |
felix |
|
todo: View
Thread,
Original
|
|
BTW. It's common to use a negative number (because of clock differences). We
use response.buffer=true response.expires = -1440 which works.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Kathy
DNRC Minister for Useful but Irritating Information and Trivia
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
----- Original Message -----
From: Phil Babcock <pbabcock(at)bgsgroup.com>
To: Bryan Bateman <batemanb(at)home.com>; <hwg-servers(at)hwg.org>
Sent: Monday, November 20, 2000 2:06 PM
Subject: Re: expiring content on win2k and IIS5 servers
We are not using the IIS Session management so this is not an option.
Fortunately I got it working using Response.ExpiresAbsolute = #January 01
2000# instead of Response.Expires = 0.
thanks for your help!
phil.
*********** REPLY SEPARATOR ***********
On 11/19/2000 at 6:22 AM Bryan Bateman wrote:
>Try Session.Timeout
>----- Original Message -----
>From: "Phil Babcock" <pbabcock(at)bgsgroup.com>
>To: <hwg-servers(at)hwg.org>
>Sent: Thursday, November 16, 2000 4:59 PM
>Subject: expiring content on win2k and IIS5 servers
>
>
>Hey all
>
>We have been fighting with trying to reliably expire the content on an IIS5
>SSL server. We have Response.Expires = 0 on every page and we have the
>server setup to allow content expiry and to expire immediately. The
trouble
>is that this only seems to cause the graphical content to be reloaded on
>each page, and not the html. For example if some one is navigating through
>the site and uses their back button, all the graphics are re-downloaded but
>the html isn't. Doing a refresh on that page then gets the new content.
>Why wasn't it requested with the graphics? We have seen some servers where
>if you use the back button you will see a page that says, "this page has
>expired.... blah blah blah". We can't seem to get that to happen on our
>machines... is there something else we need to do? Where does that "page
>has expired" that you see from time to time come from? Is that generated
by
>the browser or does it come from the server?
>
>*Any* pointers are appreciated!
>
>The servers are win2k and IIS5. We are using ASP pages.
>
>phil.
HWG: hwg-servers mailing list archives,
maintained by Webmasters @ IWA