[snapshot/master] slightly reword the caching rant
---
web/app/snapshot/templates/root.mako | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/web/app/snapshot/templates/root.mako b/web/app/snapshot/templates/root.mako
index 011d2a7..4257171 100644
--- a/web/app/snapshot/templates/root.mako
+++ b/web/app/snapshot/templates/root.mako
@@ -130,8 +130,9 @@ in cases where an entire organisation uses various apt sources.list entries on
a lot of their machines.
</p>
<p>
-Usually such entities would use proxy caches like apt-cacher and that would be
-fine if they worked correctly. Unfortunately apt-cacher completely ignores the
+Usually such entities would use proxy caches like squid and then there is no
+problem, assuming the cache works correctly. Unfortunately apt-cacher, apparently
+a common choice which is supposed to be smarter for debian archives, completely ignores the
Cache-Control headers that snapshot sends and hits this service for all
requests made to anything under <code>dist/</code>. A single <code>apt-get
update</code> can cause up to a few dozen of such requests and when multiplied
--
1.5.6.5
Reply to: