Hmmm, no replies. is this a stupid idea? If there's another workaround I'd like to know how...
--d Daisuke Maki wrote:
I have a proposal regarding headers emitted from XSP pages. I've found from some users that when they type something on a form, clicks a link to go to another page, and then come back to the same form everything they typed is gone. This seems to happen on IE 5.5 and 6, at least. Netscape 6, 7, and Mozilla seems to be immune. I've traced this to line 163 of XSP.pm: $r->no_cache(1); This adds Pragma: no-cache and Cache-Control: no-cache to the header, along with calling $AxKit::Cache->no_cache(1). The problem is that IE decides to not save anything in its local cache upon encountering "no-cache" on either of these headers. That means form values are not saved, and users complain to me. ugh. I've found out a workaround, and I think that this may work better: $r->headers_out->add( 'Cache-Control' => 'max-age=0' ); $AxKit::Cache->no_cache(1); As far as I understand, this has two effects: a) now clients (including caches in the path) will have a copy of this page b) caches that keep a copy of this page will send an IMS request every time ...and, I get to have IE keep my forms in its local cache. Anyway, I'm not 100% certain on the side effects, but this should work for most cases. Let me know if this sounds cool/stupid... --d
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
