I thought public cache was not possible when using HTTPS since every response was different (due to encryption), but just now I realized one could at least cache the unencrypted response, and the only work the server would have to do is encrypt it for each new user.
Is that how it's done by default? If not, can it be done?
I'm using nginx with fastcgi_cache.