Etags and the latest modified https SSL protocol?

Is it possible to use HTTP caching for conditional GET requests over a secure HTTPS connection? My caching works on unsafe HTTP, but when I switch to HTTPS, the browser stops sending if-none-match and if-modified-since with headers, so caching is interrupted. I tried various Cache-Control settings like public, max-age = 3600 and whatnot, boneless.

This happens both in Safari and Chrome, so I assume SSL will somehow break it. Caching not allowed over SSL?

And to be clear, the server does set etag and last-modified headers correctly, but the browser does not send if-none-match and if-modified-as in the request according to the Chrome developer tools.

Thank you for your help.

+5
source share
1 answer

I thought! Turns out you must have a trusted certificate. I used my own certificate for SSL HTTPS. Adding it to your keychain and turning it into green, caching work was performed.

+10
source

All Articles