RE: [xsl] Weird XSL refresh problem in Explorer

Subject: RE: [xsl] Weird XSL refresh problem in Explorer
From: "Hahn, Kimberly" <Kim.Hahn@xxxxxxxxxx>
Date: Tue, 21 Aug 2001 13:13:37 -0500
It may be simple caching issue.  On the project I work on we saw a lot of
really odd behavior that turned out to be caching related.  Try adding the
following to your asp script -

	Response.ExpiresAbsolute = #May 01,1999 13:30:15#
	Response.AddHeader "cache-control", "private"
	Response.AddHeader "pragma", "no-cache"

The date is arbitrary, happens to be a milestone in the development of the
project i have been on.

-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Cees Dekker
Sent: Thursday, August 16, 2001 8:03 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [xsl] Weird XSL refresh problem in Explorer

I'm having the next weird problem with client side XSL transformation, using
Explorer 5. Can someone help me to understand it?

The situation is this: from a webpage in Explorer I first call up (via <A
HREF="customerdata.php?custid=12345">) a server side generated XML file,
which is sent subsequently to my browser together with the corresponding XSL
file. The browser displays the customer information nicely, thus so far so
good. But now comes the problem when I press for whatever reason the Refresh
button in the browser. I don't get the same results again???

My question is: what is going on here? Shouldn't the same action
"customerdata.php?custid=12345" be processed at the server? And shouldn't it
give the same browser result as before? At least that is what I would expect

But it is not what I get. I get in the browser a page as if the string
'custid=123' is not sent or not processed. At least that is my conclusion
(the server side script page using php is for reasons of robustness designed
such that if the string "?custid=123" is not sent, a nice white webpage is
shown stating the missing the customer id, and that's what I get

Oeps !!!!!!!! What is going on here????????   Does somebody know what I can
do avoid this problem (for some good reasons I must stick to client side XSL
transformation), as users may also press the Refresh button?

 XSL-List info and archive:

 XSL-List info and archive:

Current Thread