When returning to a page via back/forward, Chrome reuses cached XHR responses without revalidating, even with `Cache-Control: must-revalidate`, resulting in stale content. It appears to be intentional. Anyone know how to make Chrome respect `must-revalidate` like other browsers?
I don’t know, but is the effect permanent, or only for requests made during onload?
-
-
Not sure what the precise window of effect is, but it’s not permanent.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.