Browser doesn't launches request with cache enabled
We made a simple website, with a simple link to site.com/logout url.
When i disable the browser cache the request starts and it completes without any problem.
When i enable browser cache the request doesn't starts to site.com/logout the page is refreshed with a 302 code (i don't have 302 redirects in website) and i'm unable to log the request by the browser developers tools.
In Chrome all is working fine, just in Firefox if cache is enabled it doesn't launches the GET request to site.com/logout
How can this be possible?
選ばれた解決策
You can check the HTTP response headers with the Live Http Headers extension
この回答をすべて読む 👍 0すべての返信 (6)
Reload the webpage while bypassing the cache using one of the following steps:
- Hold down the Shift key and click the Reload button with a left click.
OR
- Press Ctrl + F5 or Ctrl + Shift + R (Windows and Linux)
- Press Command + Shift + R (Mac)
Let us know if this solves the issues you are having.
Hello thanks for your answer, i tryed that but it doesn't works anyway.
So now i appended a random hash to the url and the cache is skipped so the link and requests works.
http://mysite.com/logout to -> http://mysite.com/logout?v982984774
I don't know why this happening to me only, it's weird.
Hope you'll get into deeper cause probably it still affecting many other peoples.
Hi,
If you want to leave feedback for Firefox developers, you can go to the Firefox Help menu and select Submit Feedback... or use this link. (You'll need to be on the latest version of Firefox to submit feedback). Your feedback gets collected at http://input.mozilla.org/, where a team of people read it and gather data about the most common issues.
We will get to you soon1
Report if this helps ! Thanks!
Thanks for the link, next time i'll post there ;)
Have a nice day !
選ばれた解決策
You can check the HTTP response headers with the Live Http Headers extension
Hello, thanks for support, but is it not the same to check using firebug or developers tools?
I already checked the http request params and header, the weird thing is that the request doesn't starts at all
Instead of launching GET site.com/logout it launches GET site.com -> response -> 302 moved temp -> no other information inside
And also we are unable to log GEt site.com/logout both on client and server side, this is unbelievable but true i can grant it.