View more context

 

Mo

@lerni Enabling "Disable Cache" under "Network" (in developer tools) is (I think) the recommended way to do this

Mo

Every time I have looked it up, that is what people seem to recommend

lerni

@Mo @phyzical setting browser.cache.disk.enable to false (see above) prevents the issue without having to deactivate cache in dev-console but it also prevents real-live-issues to reveal or with other words – I don’t expect clients & visitor having set that to false.

Mo

Plus, doesn't that also mean that cache will be disabled for all sites

phyzical

hmm its not what i tohught it was then, maybe the web server is doing something smart? is there maybe route caching involved external of firefox and silverstripe

lerni

well yes, but ATM it looks like more workable

phyzical

i know you said it wasnt htaccess stuff just theory crafting at this point 😄

phyzical

and opther browsers dont replicate the issue?

lerni

local env is homebrew based apache and it doesn't happen with chrome