Have looked into to using the |?date| hack to prevent caching?
You effectively append the system epoch time to the URL for the nocache
JS file in the main HTML file.
On 1/5/25 18:03, Craig Mitchell wrote:
I'm too scared to change it without someone telling me it 100% works.
😆 When I swapped from GAE legacy to GAE standard, my filter got
messed up, and people didn't get the updates correctly. The amount of
times I had to ask people to clear their cache was painful.
If we can agree on what the best filter should be, we should include
it in https://github.com/NaluKit/gwt-maven-springboot-archetype 🙂
On Sunday, 5 January 2025 at 6:12:52 am UTC+11 Thomas Broyer wrote:
On Friday, January 3, 2025 at 6:51:34 AM UTC+1 [email protected]
wrote:
Hi Craig,
there are 101 hacks to try and keep the browser from caching.
Problem is that it's a browser implementation on what to cache
and what not, and how the browser determines what to cache
when seems subject to change.
So for me I prefer to assume it doesn't work.
That's not my experience.
Note that refreshing a page is different from navigating to it
(through a link), or going back to it from the navigation history
(might also use bfcache), particularly when it comes to subresources.
Having said that; except for the last-modified flag my config
is the same as yours. I'll add it - thanks!
If it works, it works.
Fwiw,
* "Pragma: no-cache" never had a specified behavior in responses
(it was initially created for requests)
* Cache-Control is widespread (released in all browsers 11 years
ago: https://caniuse.com/mdn-http_headers_cache-control) so
you can replace Expires with a max-age directive.
* I would also use no-cache over no-store: the content of the
nocache files don't contain any user-sensitive information so
it's ok to store them as long as you revalidate with the
server that they're still up-to-date. For that, you need
Last-Modified or ETag (preferred) response headers though (you
can just use the file's modification date, or derive an ETag
from its content). If your server doesn't send those, then I'd
look for a better implementation (or work around it by
implementing it myself in a filter as suggested here)
See also
https://jakearchibald.com/2016/caching-best-practices/ and
https://web.dev/articles/http-cache#flowchart
--
You received this message because you are subscribed to the Google
Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/google-web-toolkit/19ac9860-4656-4237-81bb-fb3ab622d3a8n%40googlegroups.com
<https://groups.google.com/d/msgid/google-web-toolkit/19ac9860-4656-4237-81bb-fb3ab622d3a8n%40googlegroups.com?utm_medium=email&utm_source=footer>.
​
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/google-web-toolkit/b8a384d1-053c-4097-b3b7-ee1632922cfa%40newsrx.com.
