<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>varnish on www@aranciaga</title>
    <link>https://aranciaga.com/tags/varnish/</link>
    <description>Recent content in varnish on www@aranciaga</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 09 Apr 2024 00:08:16 -0300</lastBuildDate><atom:link href="https://aranciaga.com/tags/varnish/atom.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Varnish: dealing with web analytics</title>
      <link>https://aranciaga.com/posts/varnish-dealing-with-web-analytics/</link>
      <pubDate>Tue, 09 Apr 2024 00:08:16 -0300</pubDate>
      
      <guid>https://aranciaga.com/posts/varnish-dealing-with-web-analytics/</guid>
      <description>If you are running Varnish as cache server in a high traffic website, you are probably using web analytics software like Google Analytics for measuring user behaviour and engagement.
The problem is: you are receiving a lot of requests with unique query string parameters, such as fbclid, gclid, etc and directly impacting on your website performance. By default, Varnish will assume that a new copy of that page is necessary.</description>
    </item>
    
  </channel>
</rss>
