<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using Varnish to assist with AB Testing</title>
	<atom:link href="http://cd34.com/blog/webserver/using-varnish-to-assist-with-ab-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://cd34.com/blog/webserver/using-varnish-to-assist-with-ab-testing/</link>
	<description>This is my blog, there are many others like it but this one is mine.</description>
	<lastBuildDate>Wed, 01 Feb 2012 13:05:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: cd34</title>
		<link>http://cd34.com/blog/webserver/using-varnish-to-assist-with-ab-testing/comment-page-1/#comment-1632</link>
		<dc:creator>cd34</dc:creator>
		<pubDate>Wed, 11 Jan 2012 16:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://cd34.com/blog/?p=896#comment-1632</guid>
		<description>Modified to add vrt_magic_string_end as per Christopher Cato&#039;s debugging and DocWilco in IRC</description>
		<content:encoded><![CDATA[<p>Modified to add vrt_magic_string_end as per Christopher Cato&#8217;s debugging and DocWilco in IRC</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cd34</title>
		<link>http://cd34.com/blog/webserver/using-varnish-to-assist-with-ab-testing/comment-page-1/#comment-1413</link>
		<dc:creator>cd34</dc:creator>
		<pubDate>Tue, 04 Jan 2011 19:22:57 +0000</pubDate>
		<guid isPermaLink="false">http://cd34.com/blog/?p=896#comment-1413</guid>
		<description>Where do you set the cookie?  Since most AB Tests are testing landing pages, usually it is the first time we&#039;re seeing that particular surfer.  So, the decision needs to be made within Varnish.  Since we don&#039;t see the request hit on the backend, we have a small webbug that reports which page was served for analysis.

The only method I could think of to make and cache that decision within Varnish was to use inline C since I didn&#039;t have access to a random function in VCL.</description>
		<content:encoded><![CDATA[<p>Where do you set the cookie?  Since most AB Tests are testing landing pages, usually it is the first time we&#8217;re seeing that particular surfer.  So, the decision needs to be made within Varnish.  Since we don&#8217;t see the request hit on the backend, we have a small webbug that reports which page was served for analysis.</p>
<p>The only method I could think of to make and cache that decision within Varnish was to use inline C since I didn&#8217;t have access to a random function in VCL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: perbu</title>
		<link>http://cd34.com/blog/webserver/using-varnish-to-assist-with-ab-testing/comment-page-1/#comment-1409</link>
		<dc:creator>perbu</dc:creator>
		<pubDate>Tue, 04 Jan 2011 11:19:15 +0000</pubDate>
		<guid isPermaLink="false">http://cd34.com/blog/?p=896#comment-1409</guid>
		<description>I&#039;ve been thinking about this a bit and I don&#039;t see why we can&#039;t do persistent AB testing with Varnish. If you&#039;re set a cookie &quot;abtest&quot; to &quot;A&quot; or &quot;B&quot; and then pick up the cookie in vcl_recv and either rewrite the URL (prepending /1 or /2) or set a request header to the backend based on that cookie you could easily accomplish this. If you set a synthetic request header you could also Vary on this header increasing the cache efficiency.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been thinking about this a bit and I don&#8217;t see why we can&#8217;t do persistent AB testing with Varnish. If you&#8217;re set a cookie &#8220;abtest&#8221; to &#8220;A&#8221; or &#8220;B&#8221; and then pick up the cookie in vcl_recv and either rewrite the URL (prepending /1 or /2) or set a request header to the backend based on that cookie you could easily accomplish this. If you set a synthetic request header you could also Vary on this header increasing the cache efficiency.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://cd34.com/blog/webserver/using-varnish-to-assist-with-ab-testing/comment-page-1/#comment-1255</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Tue, 09 Mar 2010 12:30:01 +0000</pubDate>
		<guid isPermaLink="false">http://cd34.com/blog/?p=896#comment-1255</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by mcd34: blog post: Using Varnish to assist with AB Testing http://cli.gs/WYu6n #abtest #analytics #Varnish...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by mcd34: blog post: Using Varnish to assist with AB Testing <a href="http://cli.gs/WYu6n" rel="nofollow">http://cli.gs/WYu6n</a> #abtest #analytics #Varnish&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scalability links for Feb 28th 2010 &#124; Scalable web architectures</title>
		<link>http://cd34.com/blog/webserver/using-varnish-to-assist-with-ab-testing/comment-page-1/#comment-1183</link>
		<dc:creator>Scalability links for Feb 28th 2010 &#124; Scalable web architectures</dc:creator>
		<pubDate>Sun, 28 Feb 2010 08:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://cd34.com/blog/?p=896#comment-1183</guid>
		<description>[...] Using Varnish to assist with AB testing – Testing new uncooked features by external customers get more difficult as products become more mature and stable. Tools like “varnish” could be used to test different pages/features. [...]</description>
		<content:encoded><![CDATA[<p>[...] Using Varnish to assist with AB testing – Testing new uncooked features by external customers get more difficult as products become more mature and stable. Tools like “varnish” could be used to test different pages/features. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

