<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi there,</p>
<p><br>
</p>
<p>this may seem like a stupid question, but it seems I am
struggling with the Browsers' cache handling of Javascript Code.</p>
<p>Let me start by describing what happens: I change some javascript
code in my Seaside app, deploy it onto the server and restart the
image.</p>
<p>For many (but not all) users, the changes don't get downloaded
for days. They need to go to a page, press the Browser's reload
button and from then on they are fine. This is both good to know
and bad at the same time for several reasons:</p>
<ul>
<li>some users never call and are frustrated</li>
<li>the number of support cases causes high cost</li>
</ul>
<p>The effect shows up both for Javascript that gets served from the
file system (using rewrite rules) and for code served directly
from Seaside in the render* methods. <br>
</p>
<p>For the file system stuff, we have to work on the caching
settings on Apache. But I am really helpless in case of "freshly
rendered" JavaScript code. How could that even be cached by a
Browser???<br>
</p>
<p><br>
</p>
<p>Any hints are welcome</p>
<p><br>
</p>
<p>Joachim<br>
</p>
<p><br>
</p>
<p><br>
</p>
<br>
<pre class="moz-signature" cols="72">--
-----------------------------------------------------------------------
Objektfabrik Joachim Tuchel <a class="moz-txt-link-freetext" href="mailto:jtuchel@objektfabrik.de">mailto:jtuchel@objektfabrik.de</a>
Fliederweg 1 <a class="moz-txt-link-freetext" href="http://www.objektfabrik.de">http://www.objektfabrik.de</a>
D-71640 Ludwigsburg <a class="moz-txt-link-freetext" href="http://joachimtuchel.wordpress.com">http://joachimtuchel.wordpress.com</a>
Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1
</pre>
</body>
</html>