I have found that in one of the applications request filters following
is added to every response:
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
On 29/06/16 17:33, Nathan Quirynen wrote:
Hi,
I have a "weird" problem where this one image won't show up. Never had
this problem before the upgrade to 5.4 and since there have been
changes with caching, I guess it has something to do with that.
I don't know a lot about the caching Tapestry does (or in general), so
I hope someone can point me in the right direction to find the problem.
After some testing the image does not load when I use Firefox, unless
I use the reload function of Firefox that overrides the cache.
The difference I find when using this is in the request headers (for
all files):
Normal load (image does not show up):
Cache-Control: max-age=0
"Hard" reload (image does show up):
Cache-Control: no-cache
Pragma: no-cache
When inspecting the source code in Firefox, the url seems correct and
then the image does show up magically.
What could be causing this one file (next to all the other assets that
were added in the same version) to have this behaviour? Can this be
caused by Tapestry?
I have tried clearing Firefox's cache, using a computer that has not
opened the application before and also changing the version of the
application with no results...
Some pointers are appreciated!
Nathan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
