squid config changes
Since we launched the eZ Components almost two years ago we've been using squid to accelerate our PEAR channel server . Until today that never caused any problems. As part of normal routines I updated all the Debian packages on this machine and with that came now a new version of Squid. Unfortunately, this new Squid (2.6) doesn't accept the old syntax (for Squid 2.5) for HTTP acceleration mode anymore and things stopped working. After some digging I found out that:
httpd_accel_host 127.0.0.1 httpd_accel_port 8080 httpd_accel_single_host on httpd_accel_uses_host_header on
should now be:
http_port 80 defaultsite=components.ez.no cache_peer 127.0.0.1 parent 8080 0 no-query originserver acl oursites dstdomain components.ez.no http_access allow oursites
Now it all works fine again.
Comments
That's the reason I only use stable branch ;)
Have you tried Varnish instead of squid?
No, I did not. Squid is doing its job well enough so I didn't spend time trying to learn Varnish. Maybe some time :-)
Life Line
I've just finished reading Tim Peake's autobiography "Limitless".
No longer construction
I walked 2.2km in 25m25s
Confirmed a chocolate shop
Updated a company office and a cafe
I walked 6.6km in 1h11m59s
I walked 8.4km in 1h38m25s
Only test with 8.2 and later on master with Xdebug CI
Merge branch 'xdebug_3_5'
Remove expliciy path from Xdebug CI
I walked 9.6km in 1h38m09s
If you're wondering why the @Xdebug issue tracker is unavailable, I can conclusively say that it's another bout of LLM scrapers.
I walked 9.9km in 1h41m14s
I walked 1.3km in 14m45s
Created 18 benches and a grave; Updated 3 benches, a tree, and a waste_basket
I walked 6.1km in 3h9m07s
Updated a vacant business
Updated a bar
I walked 1.6km in 18m00s
Updated a pub
I walked 3.4km in 54m56s
I walked 1.9km in 23m48s
Updated a pub
I walked 3.4km in 22m41s
Updated a restaurant


Shortlink
This article has a short URL available: https://drck.me/scc-5nq