Manual for fastest browsing setup.

[ressurex]

Hi all.
is there a manual besides the default setup of Squid, that makes me do a setup to cache all browsed content ( no logs!) that my family do hence making our browsing experience much faster, since we dont visit that many different sites, but those visited a lot of times per day.

http/https !!

the default setup of squid didn't do anything seem any faster using this
https://docs.netgate.com/pfsense/en/latest/cache-proxy/setup-squid-as-a-transparent-proxy.html

[Gertjan]

IMHO :
Caching of https can't be done in the middle of the stream: it will be your browser or maybe the server. All what pfSense sees is a stream of random bits (SSL traffic) - there is no head neither tail. Nothing to cache.
So : forget about accelerating https like this.
Plain http is pretty gone these days ...

The local resolver unbound caches DNS requests - that's already working right now.

[dragoangel]

@Gertjan what the hell dns cache is you speaking!? How would this speed up load of page, trash
To answer on question:
Transparent proxy don't decrypt SSL. If you want analyze and cache SSL, you need slice it and sign by you CA. All devices in you network must trust this CA, or will not work. For devices as iOS or Android it can be breaking future due many apps have pinned ssl certs and yours mitm will broke connection for apps even smartphone trust your CA, but on desktop computer that will work ok. So maybe create separate 2 vlans for phones and PCs, and on squid configure slice only for pc subnet and transparent for mobile subnet.

[ressurex]

thanks for the replies.

i solved this by using unbound with performance tweaks.

[johnpoz]

His point is caching of http or https traffic in the hope of speeding it up for local access is pretty pointless. Unless your doing mitm on your https, there is nothing to cache. And http is pretty much gone anyway - and even if just http, its dynamic generated sites.. There is really nothing to actually cache.

The browser caches stuff anyway that can be cached - since its on the end of the https tunnel..

Other than filtering traffic, there isn't much to thinking your going to cache all that much data with your proxy these days.

Its not like the client is going to be downloading the 20KB logo image of some website 100 times a day.. The browser will cache that, etc.