New answers tagged

2

We use Squid for this; the nice thing about squid is that you can set individual expiry of objects based on a pattern match, fairly easily, which allows the metadata from the yum repo to be purged fairly quickly. The config we have which implements this: refresh_pattern (Release|Packages(.gz)*)$ 0 20% 2880 refresh_pattern (\.xml|xml\.gz)$ ...


1

we had a similar challenge and have solved it using local repos and a snapshot based storage system. We basically update the development repository, clone it for testing, clone that for staging and finally for production. The amount of disk used is limited that way, plus it's all slow sata storage and that's ok. The clients get the repository info from our ...


3

This won't solve all your tasks, but maybe this is still helpful. Despite the name, apt-cacher-ng doesn't only work with Debian and derivatives, and is a caching proxy. Specialized for package files from Linux distributors, primarily for Debian (and Debian based) distributions but not limited to those. I'm using this in production in a similar (...


0

You need to check that Squid is configured properly to check upstream on every cache request, and set the HTTP If-Modified-Since header on each request. If the upstream server sends a response with 304 Not Modified, then Squid can send the existing cache version. If the upstream server replies with a new version, then Squid can update its cache and send the ...


0

It looks like you might be using server-first SSL bumping, which according to the docs cannot handle SNI on the server and will use the server's IP as the certificate (since the server will no longer have a single hostname). Starting with Squid 3.5 there are new mechanisms called peek and stare that allow squid to observe the SNI negotiation to figure out ...


0

It's not that Squid is changing it from HTTP to HTTPS, it's that NAT reflection doesn't apply to traffic initiated by the host itself (which is the case for Squid). Traffic from the LAN hosts would hit the reflection. So what you're hitting is actually the web GUI of the firewall, not your internal server. That's where the HTTP to HTTPS redirect comes from. ...



Top 50 recent answers are included