News for hackers. Stuff that matters.
Re:New HTTP standards for caching on the modern web by toast0 on Thursday October 21, 2021 @06:31PM (#28951629)
There's no standard way for one page to invalidate another. I've seen some private patches to do it in squid, but that doesn't help because you want to do it for browsers.

Your options are probably:

a) redirect to a different URL as you've done by appending stuff to it

b) require revalidation on each request, recipies shown by other posters

c) POST to the url you want refreshed; post isn't cachable. Note that you can't redirect to POST somewhere else, but you can do it with javascript.

d) use XHR to force a request as another poster mentioned.

Re:New HTTP standards for caching on the modern web by bawolff on Thursday October 21, 2021 @08:16PM (#28952432)
E) use webworkers

Not saying its the right option, but it is an option.

Re:New HTTP standards for caching on the modern web by rob-olmos on Thursday October 21, 2021 @07:05PM (#28951905)
for (c), HTTP 307 doesn't work?
Re:New HTTP standards for caching on the modern web by toast0 on Thursday October 21, 2021 @07:49PM (#28952257)
Apparently, yes. My webfoo is a bit dated.