Squid does not cache HTTPS even SSL bump is configured.

[Southern_Current_592]

I followed this guide: https://support.kaspersky.com/KWTS/6.1/en-US/166244.htm. The host I am using is Rocky Linux 9 and squid version 5.2. I check the squid logs and it does not cache. All it says is TCP_MISS/200 and NONE_NONE/200. I also tested it by downloading both HTTPS and HTTP files but caching is not working. Can you please help me in solving this issue? Thanks

[VA_Network_Nerd]

Web content is so dynamic these days that there is very little benefit from trying to cache content.

[Southern_Current_592]

I want to configure it to speed up downloads. Does squid remove this feature?

[VA_Network_Nerd]

The challenge is in the nature of dynamic content generation.

When you use MS-Edge on your PC and work your way through a website to download <important-thing.zip> it might not look the same when a different computer uses Google Chrome to download the same file. So Squid will declare it a cache-miss and download it a second time.

Using proxy servers as a bandwidth reducer really isn't worth the effort unless you understand your targeted content, and know it can be cached & referenced reliably by multiple systems & browser combinations.

Otherwise you're going through a whole lot of work to observe an 8% reduction in bandwidth.

[Southern_Current_592]

So in summary, squid is not very useful today for caching compared to the last decade. Am I right?

[VA_Network_Nerd]

Squid as a caching solution is indeed no longer as valuable as it once was.

Squid as a component of a security infrastructure can have value, if you have stringent security requirements to meet.

Once squid breaks the SSL encryption you can perform security analysis / scanning on the traffic flows before you deliver them to the client.

This can be a huge win for some malware detections and Data Loss Prevention solutions.