I'm working on dynamic HTTP 301 Redirect responses for an ASP.Net project, and they are cached correctly in Firefox, but no matter what I set the cache headers to, the redirect is never cached by Chrome:
Headers General:
Request URL:https:// domain /old/spot
Request Method:GET
Status Code:301
Remote Address:127.0.0.1:443
Referrer Policy:no-referrer-when-downgrade
Response Headers:
cache-control:private, max-age=3600
content-length:0
content-type:text/html
date:Fri, 27 Oct 2017 14:03:28 GMT
expires:Fri, 27 Oct 2017 15:03:28 GMT
location:/blog1/test
server:Microsoft-IIS/10.0
status:301
Request Headers:
:authority: domain
:method:GET
:path:/old/spot
:scheme:https
user-agent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
With self-signed SSL certificates, Chrome ignores all caching directives and reloads the content ... This is a known issue with Chrome browser. It does not cache responses if the HTTPS connection is using an invalid Certificate. See this bug report for details: https://bugs.chromium.org/p/chromium/issues/detail?id=110649#c8
We're going to work around by testing with a valid certificate and HOST file changes.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.