That's not what I wanted to say, I wanted to say "https may cause troubles with caching", In fact some caching servers have problems with https since the header is encrypted as well, so they usually just forward the encrypted traffic to server. I don't say it's impossible to cache this, but it's very complicated
On Sun, Apr 1, 2012 at 6:43 PM, Antoine Musso hashar+wmf@free.fr wrote:
Le 01/04/12 12:55, Petr Bena wrote:
I see no point in doing that. Https doesn't support caching well and is generally slower. There is no use for readers for that.
HTTPS has nothing to do with caching, it just transports informations between the client and the server so they can actually handle caching.
HTTPS supports caching as well as HTTP since they are exactly the same protocol, the first just being encrypted.