purge Javascript cache
adamjrice opened this issue · comments
It seems that some issues people encounter while using the registration issues get solved, but the solutions don't reach them until they purge their caches. Force a purge when there's an update to bypass this step.
Or they wait one hour. We have a very low cache bar as is. Not much else I can do but completely remove caching...
Patrick,
If the javascipt is static,add the ETag to the response header.
The browser will send its ETag on the next request for you to compare with
the ETag computed for the static file.
If the ETags are the same, the server sends a 304, else it sends the file
content with a 200.
M$ sets the ETag to ((file last modified file time)^ file length ) to base
16 string.
Treg
…On Mar 5, 2018 1:43 PM, "Patrick Boyd" ***@***.***> wrote:
Or they wait one hour. We have a very low cache bar as is. Not much else I
can do but completely remove caching...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAvMbKVhFgGLCloJm0oQIpSH6lFDjp6Jks5tbZVwgaJpZM4SW1Ox>
.
ETag is set:
ETag: "4110-5662a93701ee0"
I've just never seen a browser except Chrome honor it. And if you throw proxy's in there it gets messier.