Monday, May 30, 2011

Codesplitting and ``If-Modified-Since`` Header

Hey,

we are successfully using the codesplitting feature in our project. on
our staging server, i recognized that all splitted files are always
completely loaded from the server. All files included in the hostpage,
will send a ``If-Modified-Since`` header the second time I load the
app::

If-Modified-Since Mon, 30 May 2011 14:29:42 GMT
Cache-Control max-age=0

All splitted JS files are correctly loaded afterwards, but the problem
is they never contain these information (``If-Modified-Since``
header). So the server is not able to respond with a 304 Not
Modified.

Can someone give me a hint where to tweak this behaviour?

The advice given here:
http://code.google.com/intl/de-DE/webtoolkit/doc/latest/DevGuideCompilingAndDebugging.html#perfect_caching
also wont work without that header.

Thanks, Andi

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

No comments:

Post a Comment