New answers tagged


SSL/TLS is a transport encryption standard. It hides the entire communication between client and server. So decryption of the transport encryption* is a prerequisite to caching. Intercepting SSL/TLS is something that does happen, but mostly on private networks or by ISPs in totalitarian regimes. It's not something that can really be done without users ...


If they provide an HTTP proxy service you use, they can cache on the fly. If they do not pervert the HTTPS stream (which starts by changing the server certificate exposed and/or changing the CAs you trust on your client device) they have no way to see the content, hence they have nothing to cache.


FTP is a seperate service to https, normally handled with different software. You likely need to update the certificate settings for the FTP server and restart it.


To clarify what @StephenOstermiller mentioned in comments, nothing has changed in this regard for quite literally decades. Any question you find on the Stack Exchange network, regarding canonical redirects on Apache, will be just as relevant now it was "back in the day". There is also no single "correct" solution. Due to the variation of ...


You should not remove HTTP to HTTPS redirects. Removing them won't fix performance problems. Redirects only make it slower when users encounter them and most users should never see the redirects. Once a user is on your site (, all the links should keep the https and www. Users should never need the redirects once they are on the ...

Top 50 recent answers are included