{
  "id": "https://mort.io/blog/looping-the-loop/",
  "title": "Looping the Loop",
  "link": "https://mort.io/blog/looping-the-loop/",
  "updated": "2015-02-17T00:00:00",
  "published": "2015-02-17T00:00:00",
  "summary": "<p>In a fit of blogging mania, here’s another one literally barely days after the\nprevious one. Maybe I’ll crack this yet.</p>\n<p>Anyway, this is just a short one with what verges on a Technical Contribution.\nTo whit: I recently sorted out <a href=\"http://mort.io/\">this domain</a> and was having\nsome issues getting some consistency between what <code>dig</code>, Chrome and my\n<a href=\"http://gandi.net\">domain provider</a> believed to be the correct state. In\nparticular, I was switching over to make the domain properly live rather than\nsimply a <code>301 Moved Permanently</code> redirect to my old pages at Nottingham.</p>\n<p>It turns out this was probably mostly Chrome being confused. It seems that it\ncaches <code>301 Moved Permanently</code> redirects fairly aggressively and the cached\nentries are <strong>not</strong> discarded when you go through the standard mechanisms to\nclear caches.</p>\n<p>After a bit of experimentation and browsing, it seems that one way to clear this\nis to <code>view-source</code> on the page but pass a spurious parameter to defeat the\ncache. So, to force the browser to fetch <a href=\"http://mort.io\">http://mort.io</a> properly, all I had to\ndo was <code>view-source:mort.io?spurious=parameter</code>. And lo! All was well.</p>",
  "content": "<p>In a fit of blogging mania, here’s another one literally barely days after the\nprevious one. Maybe I’ll crack this yet.</p>\n<p>Anyway, this is just a short one with what verges on a Technical Contribution.\nTo whit: I recently sorted out <a href=\"http://mort.io/\">this domain</a> and was having\nsome issues getting some consistency between what <code>dig</code>, Chrome and my\n<a href=\"http://gandi.net\">domain provider</a> believed to be the correct state. In\nparticular, I was switching over to make the domain properly live rather than\nsimply a <code>301 Moved Permanently</code> redirect to my old pages at Nottingham.</p>\n<p>It turns out this was probably mostly Chrome being confused. It seems that it\ncaches <code>301 Moved Permanently</code> redirects fairly aggressively and the cached\nentries are <strong>not</strong> discarded when you go through the standard mechanisms to\nclear caches.</p>\n<p>After a bit of experimentation and browsing, it seems that one way to clear this\nis to <code>view-source</code> on the page but pass a spurious parameter to defeat the\ncache. So, to force the browser to fetch <a href=\"http://mort.io\">http://mort.io</a> properly, all I had to\ndo was <code>view-source:mort.io?spurious=parameter</code>. And lo! All was well.</p>",
  "content_type": "html",
  "author": {
    "name": "Unknown",
    "email": null,
    "uri": null
  },
  "categories": [],
  "source": "https://mort.io/atom.xml"
}