Databases
StackOverflow2013
Postsdbo
POVarnish - 2 projects different behaviour
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POVarnish - 2 projects different behaviour
    primarykey
    data
    text
    <p>I have 2 django projects, setup basically the same. They both are a News/Article page, and the problem is with the second one. The first project caches correctly (index page and article page), although the second one caches only the home page, for example:</p> <p>Project 1 Home page:</p> <pre><code>curl -X PURGE http://teste.infalms.com.br/ (response: 200[hit] purged) </code></pre> <p>Project 1 Article page:</p> <pre><code>curl -X PURGE http://teste.infalms.com.br/noticias/variedades/pqp-hein/ (response: 200[hit] purged) </code></pre> <p>Project 2 Home page:</p> <pre><code>curl -X PURGE http://pcmag.infalms.com.br/ (response: 200[hit] </code></pre> <p>Project 2 Article page (404 [miss] Not in cache.):</p> <pre><code>curl -X PURGE http://pcmag.infalms.com.br/noticias/google-street-view-continua-capturando-momentos-estranhos/ 404 [miss] Not in cache. </code></pre> <p>Here is my default.vcl:</p> <pre><code>backend teste { .host = "127.0.0.1"; .port = "8080"; } acl purge { "localhost"; "127.0.0.1"; "198.58.107.57"; } sub vcl_recv { # unless sessionid/csrftoken is in the request, don't pass ANY cookies (referral_source, utm, etc) if (req.request == "GET" &amp;&amp; (req.url ~ "^/static" || (req.http.cookie !~ "sessionid" &amp;&amp; req.http.cookie !~ "csrftoken"))) { remove req.http.Cookie; } # normalize accept-encoding to account for different browsers # see: https://www.varnish-cache.org/trac/wiki/VCLExampleNormalizeAcceptEncoding if (req.http.Accept-Encoding) { if (req.http.Accept-Encoding ~ "gzip") { set req.http.Accept-Encoding = "gzip"; } elsif (req.http.Accept-Encoding ~ "deflate") { set req.http.Accept-Encoding = "deflate"; } else { # unknown algorithm remove req.http.Accept-Encoding; } } # allow PURGE from localhost and 192.168.55... if (req.request == "PURGE") { if (!client.ip ~ purge) { error 405 "Not allowed."; } return (lookup); } if (req.request == "BAN") { ban("obj.http.x-url ~ " + req.http.x-ban-url + " &amp;&amp; obj.http.x-host ~ " + req.http.x-ban-host); error 200 "Banned"; } if (req.request == "REFRESH") { set req.request = "GET"; set req.hash_always_miss = true; } if (req.http.host ~ "pgadmin.infalms.com.br" || req.url ~ "admin" || req.http.host ~ "mediatarget.com.br" || req.http.host ~ "www.mediatarget.com.br") { return(pass); } } sub vcl_fetch { if (beresp.ttl &gt; 0s) { /* Remove Expires from backend, it's not long enough */ unset beresp.http.expires; /* Set the clients TTL on this object */ set beresp.http.cache-control = "max-age=900"; /* Set how long Varnish will keep it */ set beresp.ttl = 1w; /* marker for vcl_deliver to reset Age: */ set beresp.http.magicmarker = "1"; } # static files always cached if (req.url ~ "^/static") { unset beresp.http.set-cookie; return (deliver); } # pass through for anything with a session/csrftoken set if (beresp.http.set-cookie ~ "sessionid" || beresp.http.set-cookie ~ "csrftoken") { return (hit_for_pass); } else { return (deliver); } } sub vcl_deliver { if (resp.http.magicmarker) { /* Remove the magic marker */ unset resp.http.magicmarker; /* By definition we have a fresh object */ set resp.http.age = "0"; } } sub vcl_hit { if (req.request == "PURGE") { purge; error 200 "[hit] Purged."; } } sub vcl_miss { if (req.request == "PURGE") { purge; error 404 "[miss] Not in cache."; } } </code></pre> <p>There's another problem with Varnish, which is the fact that some images are not cached and not loading at all. Like this one:</p> <pre><code>http://pcmag.infalms.com.br/media/oldsite_imgs/bodytext_img_862920.jpg </code></pre> <p>When I try to purge it, it returns a [404]Miss. It loads sometimes if I keep pressing F5, but it's totally random.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMauricio
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POVarnish - 2 projects different behaviour
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POVarnish - 2 projects different behaviour
      1. USGustavo Siqueira
      1. VTFavorite
    3. VO
      singulars
      1. POVarnish - 2 projects different behaviour
      1. USMauricio
      1. VTFavorite
    1. COWhat is the varnishlog output during a 404 for that image? Perhaps the headers from the origin exceed the headers buffer size, or perhaps the origin times out? Could you print out the headers the backend is returning to varnish in each case? My guess is that will inform you about why the second article page isn't caching.
      singulars
      1. POVarnish - 2 projects different behaviour
      1. USJohnny C
    2. COAlso resetting the Age header to 0 makes it hard to tell when responses from varnish were cache hits or not. I'm not sure why you're doing that?
      singulars
      1. POVarnish - 2 projects different behaviour
      1. USJohnny C
    3. COThanks for replying. It's not a 404 that comes from the request. It is a "No data received" as you'll see at this print http://screencloud.net/v/iLwm
      singulars
      1. POVarnish - 2 projects different behaviour
      1. USMauricio
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload