[Support Request] XHR request may read cache by browser which conflict the purpose of ajax request about core-ng-project HOT 3 CLOSED

i am not aware of any ajax response is cached in react application,
so for 5), can you clarify whether page A doesnt send ajax request when goes back, or page sent request (you can see it thru chrome dev tools network), but it got cached (dev tool will show memory cache or disk cache in size column)?
and check whether server side sends any cache-control header? (not supposed to have)

from core-ng-project.

I confirmed that the API request triggered by backing-up action was used with disk cached. The frontend fixed this bug. I will try to recreate this bug by writing a react demo, if I can do so I will reopen this issue.

from core-ng-project.

ok, please update me if you are able to reproduce,

i did quick test, if there is no cache-control header in response, i don't see chrome caches the xhr get request,
i think you may want to double check the response header of the cached ajax call.

if cache-control: no-store is needed (usually you want to add this header for index.html response)
then you can still do it via interceptor, but i haven't encountered any cases like what you said

from core-ng-project.