Chrome pretends to refresh a page with HTTP 500 error
Reported by
francesc...@gmail.com,
Jul 2 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Create a web-page on a server you can control, and let this page generate an HTTP 500 error 2. Start tailing your webserver's access logs 3. Go to that page and get the Chrome 500 error 4. Edit your page so that it returns an HTTP 200 with some content 5. Return to Chrome and try to refresh the page (no matter how, CMD+R, the refresh button, etc) 6. Chrome still shows the HTTP 500 error page, because it doesn't try to reload the page. You can try several times if you wish 7. Check your webserver logs tailing, you won't notice the second request (or third, fourth, whatever) 8. Open the developer tools, and go to the "Network" tab 9. Try to reload the page again 10. This time Chrome will refresh the page correctly and you will get the content of the page Instead of having a webserver in your hand, you can just use a proxy app like Charles, and see that no HTTP request are fired when you get the 500 for the first time (until you open the Developer Tools) What is the expected behavior? Chrome should refresh the page for real firing the HTTP request and get the new content without open the Developer Tools What went wrong? If you're developing a web-application, and you get an HTTP 500 error, you correct your code, and then you refresh the page to see the effects. I've spent more than half an hour trying to understand why the corrected code was returning a 500 again and again and again, but it was just Chrome not refreshing the page. Did this work before? N/A Chrome version: 51.0.2704.103 Channel: stable OS Version: OS X 10.11.2 Flash Version: Shockwave Flash 22.0 r0
,
Jul 6 2016
Could you provide a net internals dump for this? The process for doing so is described here: https://dev.chromium.org/for-testers/providing-network-details
,
Jul 6 2016
Please find enclosed the exported file. I've generated a 500 HTTP error calling an undefined PHP function, tried to load the page, and got the 500 error page. Then corrected the error, and tried to refresh the page several times with the refresh button, CMD+R and the "Reload" button on the 500 page. Nothing changed (the page flashes like a quick refresh action). Then opened the Developer Tools, switched to the Network tab, tried to reload the page, and got an HTTP 200 with a random string.
,
Jul 7 2016
Thank you for providing more feedback. Adding requester "bmcquade@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 9 2016
Unassigning myself so next triager can take a look.
,
Jul 15 2016
According to the NetLog dump, the headers are being modified by your extension (Adblock Plus, in this case). Could you disable your extensions and try again?
,
Jul 27 2016
Looking at the log, the server was returning 500 errors for all the reloads, up until the last request (Which happened 6 seconds after the last 500 request). Your server sends "Age: 1" for the second response, and ~19 seconds later, sends "Age: 20" for the last 500 response. I suspect this means your webserver is caching the 500 response in memory for 20 seconds, and that this isn't a Chrome issue. You didn't mention it, but I assume you see this behavior in other browsers? Going to go ahead and close this issue, due to lack of response, and this looking like a webserver issue.
,
Jul 27 2016
Sorry for running late, have been quite busy in the last few days. As xunji said, it was AdBlockPlus to cause this problem. No it was not a webserver caching issue, since with Safari and FireFox I was not experiencing this issue. The error in other browser disappears as soon as I edit the script that is causing it. Instead in Chrome it was stuck on the 500 page, until opening the Network tab. I will report the bug to AdBlock developers, and will disable AdBlock on my websites in the mean time. Thanks for the support everyone, this can be closed. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by durga.behera@chromium.org
, Jul 4 2016