varnish

I have to cache multiple backend servers, I switch from Nginx to Varnish and finally discover 2 server need to run HTTP Basic Authentication. I try this link http://blog.tenya.me/blog/2011/12/14/varnish-http-authentication and it not work for me (they ran Varnish 3) Is there an easy way to configure Basic Authentication in Varnish 4? You can use the VMOD basicauth Install the Varnish VMOD First you need to install it. Download the source from the Git repo for basicauth . Extract into your homedir e.g. ~/vmod-basicauth/ You'll also need the Varnish source to build the VMOD. In Debian/Ubuntu

Im wondering how the performance of th ESI module is nowadays? I've read some posts on the web that ESI performance on varnish were actually slower than the real thing. Say i had a page with over 3500 esi includes, how would this perform? is esi designed for such usage? We're using Varnish and ESI to embed sub-documents into JSON documents. Basically a response from our app-server looks like this: [ <esi:include src="/station/best_of_80s" />, <esi:include src="/station/herrmerktradio" />, <esi:include src="/station/bluesclub" />, <esi:include src="/station/jazzloft" />, <esi:include src="

可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: Problem : I couldn't purge my page. After many time I decided to find out how purge works and find! As you can see we have used a new action - return(purge). This ends execution of vcl_recv and jumps to vcl_hash. This is just like we handle a regular request. When vcl_hash calls return(lookup) varnish will purge the object and then call vcl_purge. Here you have the option of adding any particular actions you want Varnish to take once it has purge the object. docs And then I understood that I have cookie in hash_data and I can't purge

可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: following situation: On the server is a apache and Varnish for caching. SSL is handled by an amazon load balancer. If the page is requested using https, the http header "X-Forwarded-Proto" is set to "https". The pages are sometimes different (e.g. links/images have to be fetched using https when using a secure connection) How can I tell varnish that pages are different if the X-Forwarded-Proto header differs? As it is now, whatever is accessed first is cached and served for http and https! 回答1: What you want, I presume, is to have different