Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.
clear cache does not clear all the cache
Hi, After clearing the cache, the browser assumes some of the files are still cached so it won't try to get the file from the server. This causes the website to hang as it does not timeout.
It does not always happen, for example in my machine is OK, but a colleague's machine has it consistently and other people too. The only way that they could make it work is going to about:support and doing a reset.
The Troubleshooting Information I've added is from the problematic machine.
Alle svar (4)
Are they using built-in means to clear the cache or external (cleanup) programs?
You can try to delete the cache folder.
You can find the location of the cache on the about:cache page.
The "Application Data" folder in XP/Win2K and the "AppData" folder in Windows Vista and Windows 7 and later versions are hidden folders.
They use the built-in means to clear the cache. Tried deleting the cache folder but it did not help. Tried also deleting the profile folder contents and it did work. I guess that is similar to reset functionality.
Still, if clearing the cache folder worked would be a a workaround for us, as developers but not something we could ask from our customers.
You can try it with this URL: https://hornbill.socialworkforce.com/socialworkforce/user/lib/hux/server/comboloader/comboloader.php?ver=1.1.0&../../ext/yui3/../../../esp_hux/components/Xmlmc/Xmlmc-min.js
Again, they are able to load it for the first time, but if they clear the cache, they cannot get the response from that url, in fact there is not even a request from the browser.
What makes you think that the cache isn't cleared?
You can check the current cache usage on the about:cache page.
We checked already in about:cache and it shows 0kb (0 entries) but when trying to load the file, "I think" it thinks that file is still cached (but is not) so it is not trying to load it again.
In a normal scenario, that URL should return a 304 status from the server, but in this case the is not even a request. I've tested it with a sniffer and there is no network activity. But if I change for example the GET parameter "ver" to something else (for example 1.1.1), it works.
I tried to reproduce it in my machine, same OS version, same FF version but is working, but we have already 5 people with the same problem.