* Alex Rousskov <rouss...@measurement-factory.com>: > > > 2023/09/27 22:42:57| ERROR: Squid BUG: assurance failed: > > > tok.skip(WellKnownUrlPathPrefix()) > > > exception location: cache_manager.cc(193) ParseUrl > > > current master transaction: master59170 > > That bug has been fixed in master/v7. For details, including confusing v6.3 > status and a v6.3 patch, please see the beginning of > https://lists.squid-cache.org/pipermail/squid-users/2023-September/026093.html
... > Short answer: Use `squidclient ... mgr:counters` Ah, much better. Now I'm getting access denied, which is way better. > Long answer: For a long time, squidclient has supported two cache manager > protocols (or two URI schemes): Deprecated cache_object and regular http > (with a well-known URL path prefix). It now relies on the latter > exclusively. Good. I figured as much, but wasn't able to find the "new style" > The "mgr:foo" shorthand used to expand to cache_object://host/foo > It now expands to http://host/squid-internal-mgr/foo > You are welcome to use the latter explicitly if you prefer. Indeed, I'm now using curl with the URL http://host/squid-internal-mgr/foo -- Ralf Hildebrandt Charité - Universitätsmedizin Berlin Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration Invalidenstraße 120/121 | D-10115 Berlin Tel. +49 30 450 570 155 ralf.hildebra...@charite.de https://www.charite.de _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org https://lists.squid-cache.org/listinfo/squid-users
