I have cleared the browser cache, and have restarted the browser, but Chrome still
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The reason for the status you’re getting is most likely a result of the two headers at the bottom of your screenshot:
If-Modified-SinceandIf-None-Match. These are detailed here.Basically, these headers say to the server that if the conditions in the header are met, send the resource (with a
200response). If the conditions are not met, send a304response. So, IIS thinks that the file has not been modified since 25 June and that its etag is the value in theif-none-matchheader.There could be a number of reasons for this depending on your IIS configuration and what, exactly, is being served. Firefox is likely working because it’s not sending those headers.