I think you can set content expiry somehow. May be you can tell
the browser that the page expires immediately. I believe that this is
different from "nocache" directive.
I have noticed this problem with IE during testing.. would be keen
to know how one can force the browser to trash the cache.
On 29 Mar 00, at 9:38, Mehul Harry wrote:
From: "Mehul Harry" <mehulh@c...>
To: "Code Clinic" <proasp_codeclinic@p...>
Subject: [proasp_codeclinic] RE: Self Referencing Pages and Proxy Server
Date sent: Wed, 29 Mar 2000 09:38:46 -0800
Send reply to: "Code Clinic" <proasp_codeclinic@p...>
> Try this site, it has everthing you would probably want to know about proxy
> > -----Original Message-----
> > From: Jon Ratcliffe
> > Sent: Wednesday, March 29, 2000 12:00 AM
> > To: Code Clinic
> > Subject: [proasp_codeclinic] Self Referencing Pages and Proxy Server
> > Has anybody come accross this before?
> > I have produced an ASP page that contains HTML form elements - the idea
> > being that a user of the site fills in the various form elements with
> > data,
> > hits submit and all the data gets written to a database - Nothing
> > particularly groundbreaking here.
> > The page is self validating, in that several of the form elements NEED to
> > be filled in before a user can successfully submit the form. This is done
> > by feeding the page back to itself using the SCRIPT_NAME server variable
> > with a query string such as ?validate=yes attached to it. Again, this is
> > fairly standard stuff.
> > Here is my problem...
> > (This problem only occurs if the page is veiwed via a proxy server - which
> > in this case is about 90% of my audience!!)
> > If the validation process is used more than once (ie; the page is called
> > with the query string ?validate=yes), which it quite often will be, proxy
> > server tries to send a cached version of the page (which will obviously
> > not
> > have any ASP whatsoever in it as it will be the fully parsed HTML file) to
> > the user. This completely screws up the whole process because the page
> > that
> > the user submitted is expecting an ASP page and recieves the standard HTML
> > page.
> > I have tried a couple of things to get around this, namely putting the
> > following into the page:
> > response.CacheControl = "Private"
> > response.AddHeader "PRAGMA","NO-CACHE"
> > However this doesn't seem to stop the page from caching AT ALL!
> > If anyone has any cool workarounds for this, I would love to hear about
> > them!
> > JR
> > ---
> > You are currently subscribed to proasp_codeclinic.
> > $subst('Email.Unsub')
> You are currently subscribed to proasp_codeclinic.