From phk at phk.freebsd.dk Wed Nov 15 11:02:55 2017 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Wed, 15 Nov 2017 11:02:55 +0000 Subject: missing repo -> packagecloud redirects ? Message-ID: <65960.1510743775@critter.freebsd.dk> Varnish-cache.org is seeing a LOT of traffic from package tools looking for the old repo.varnish-cache.org Maybe somebody with more linux-package-clue than me should ponder if we can set up some strategic redirects to package-cloud ? Alternatively, if there is some HTTP response we can send which alerts these users to their predicament ? For reference, the homepage comes in just below 10 in varnishtop traffic: 70.46 ReqURL /debian/dists/jessie/Release 70.23 ReqURL /debian/dists/jessie/InRelease 67.62 ReqURL /debian/dists/jessie/Release.gpg 60.81 ReqURL /redhat/varnish-3.0/el6/x86_64/repodata/repomd.xml 57.90 ReqURL /redhat/varnish-3.0/el5/x86_64/repodata/repomd.xml 54.32 ReqURL /debian/dists/jessie/varnish-4.1/i18n/Translation-en 54.09 ReqURL /debian/dists/jessie/varnish-4.1/i18n/Translation-en.gz 53.84 ReqURL /debian/dists/jessie/varnish-4.1/i18n/Translation-en.lzma 53.72 ReqURL /debian/dists/jessie/varnish-4.1/binary-amd64/Packages 53.65 ReqURL /debian/dists/jessie/varnish-4.1/i18n/Translation-en.xz 53.51 ReqURL /debian/dists/jessie/varnish-4.1/binary-amd64/Packages.gz 53.34 ReqURL /debian/dists/jessie/varnish-4.1/i18n/Translation-en.bz2 53.28 ReqURL /debian/dists/jessie/varnish-4.1/binary-amd64/Packages.lzma 53.04 ReqURL /debian/dists/jessie/varnish-4.1/binary-amd64/Packages.xz 52.79 ReqURL /debian/dists/jessie/varnish-4.1/binary-amd64/Packages.bz2 50.35 ReqURL /debian/dists/jessie/varnish-4.1/binary-amd64/Packages.diff/Index 36.30 ReqURL /debian/dists/jessie/varnish-4.1/i18n/Translation-en_US 36.16 ReqURL /debian/dists/jessie/varnish-4.1/i18n/Translation-en_US.gz 35.95 ReqURL /debian/dists/jessie/varnish-4.1/i18n/Translation-en_US.lzma 35.78 ReqURL /debian/dists/jessie/varnish-4.1/i18n/Translation-en_US.xz 35.62 ReqURL /debian/dists/jessie/varnish-4.1/i18n/Translation-en_US.bz2 32.07 ReqURL /debian/dists/wheezy/Release 31.48 ReqURL /debian/dists/wheezy/Release.gpg 23.95 ReqURL /debian/dists/wheezy/varnish-3.0/i18n/Translation-en 23.92 ReqURL /debian/dists/wheezy/varnish-3.0/binary-amd64/Packages 23.87 ReqURL /debian/dists/wheezy/varnish-3.0/i18n/Translation-en.gz 23.86 ReqURL /debian/dists/wheezy/varnish-3.0/binary-amd64/Packages.gz 23.82 ReqURL /debian/dists/wheezy/varnish-3.0/i18n/Translation-en.lzma 23.80 ReqURL /debian/dists/wheezy/varnish-3.0/binary-amd64/Packages.lzma 23.76 ReqURL /debian/dists/wheezy/varnish-3.0/i18n/Translation-en.xz 23.75 ReqURL /debian/dists/wheezy/varnish-3.0/binary-amd64/Packages.xz 23.71 ReqURL /debian/dists/wheezy/varnish-3.0/i18n/Translation-en.bz2 23.70 ReqURL /debian/dists/wheezy/varnish-3.0/binary-amd64/Packages.bz2 23.69 ReqURL /redhat/varnish-4.1/el6/x86_64/repodata/repomd.xml 23.65 ReqURL /ubuntu/dists/lucid/Release 22.02 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-amd64/Packages.gz 21.86 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-amd64/Packages.lzma 21.82 ReqURL /ubuntu/dists/lucid/Release.gpg 21.67 ReqURL /redhat/varnish-4.0/el6/x86_64/repodata/repomd.xml 21.67 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-amd64/Packages.bz2 21.59 ReqURL /ubuntu/dists/lucid/varnish-3.0/i18n/Translation-en 21.30 ReqURL /ubuntu/dists/lucid/varnish-3.0/i18n/Translation-en.gz 21.18 ReqURL /ubuntu/dists/lucid/varnish-3.0/i18n/Translation-en.lzma 21.04 ReqURL /debian/dists/squeeze/Release 21.02 ReqURL /debian/dists/squeeze/Release.gpg 21.02 ReqURL /ubuntu/dists/lucid/varnish-3.0/i18n/Translation-en.xz 21.01 ReqURL /ubuntu/dists/lucid/varnish-3.0/i18n/Translation-en.bz2 20.71 ReqURL /redhat/varnish-4.0/el7/x86_64/repodata/repomd.xml 20.25 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-amd64/Packages 20.18 ReqURL /redhat/varnish-4.1/el7/x86_64/repodata/repomd.xml 19.69 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-amd64/Packages.xz 19.52 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-amd64/Packages.diff/Index 18.08 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-i386/Packages.gz 17.96 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-i386/Packages.lzma 17.95 ReqURL /ubuntu/dists/trusty/Release 17.86 ReqURL /ubuntu/dists/trusty/InRelease 17.86 ReqURL /debian/dists/wheezy/varnish-3.0/binary-amd64/Packages.diff/Index 17.80 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-i386/Packages.bz2 17.49 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-i386/Packages 16.98 ReqURL /ubuntu/dists/lucid/varnish-3.0/binary-i386/Packages.xz -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From jm.camalo at gmail.com Tue Nov 28 18:23:06 2017 From: jm.camalo at gmail.com (=?UTF-8?B?Sm9zw6kgTWFyw61hIEMuQS4=?=) Date: Tue, 28 Nov 2017 19:23:06 +0100 Subject: Max_esi_depth and nested Esi Message-ID: Hi, I am working with varnish 4.1.8. Im using nested esis and the default level was 5. I made several html components that they need 9 depth levels and I have changed the max_esi_depth to 9. My question is: which are the consequences of this parameter regarding to this increment of level, maybe increase the processing time per esi? Thnaks in advance ?? -------------- next part -------------- An HTML attachment was scrubbed... URL: From slink at schokola.de Thu Nov 30 19:39:22 2017 From: slink at schokola.de (Nils Goroll) Date: Thu, 30 Nov 2017 20:39:22 +0100 Subject: Max_esi_depth and nested Esi In-Reply-To: References: Message-ID: please keep user questions on the -misc mailing list. Thank you!