Re: Weird XSL refresh problem in Explorer

It sounds like you need to set the "expires" heading in the HTTP
header to 0 (zero) in order to force your "Refresh" button to
fetch the document from the server instead of using the Web
brower's cache.  Quoting from the Apache docs:

    The Expires HTTP header is an instruction to the client
    about the document's validity and persistence.  If cached,
    the document may be fetched from the cache rather than from
    the source until this time has passed.  After that, the
    cache copy is considered "expired" and invalid, and a new
    copy must be obtained from the source.


/s/ Ernest G. Allen

- - -

"Cees Dekker" <cees.dekker@xxxxxxxx> wrote...
>Date: Thu, 16 Aug 2001 15:02:49 +0200
>From: "Cees Dekker" <cees.dekker@xxxxxxxx>
>Subject:  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 unfortunately).
>
>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:  http://www.mulberrytech.com/xsl/xsl-list