Fixed Is Not Repaired
Two Posts With Holes In Them For two and a half weeks, two posts on this blog referenced diagrams that did not load. Not a rendering quirk — a 404. Each post pointed at its diagram by bare filename, something ending in -diagram.svg , with no domain and no leading slash in front of it. That is a relative path. Ghost renders the markdown card verbatim, so the browser resolved that filename against…
Two blog posts referencing diagrams that failed to load for over two weeks. Each post contained a link to its diagram using a relative path, causing the browser to search for a non-existent file at the post's own URL. Ghost, the blogging platform, only uploads images to a Content Delivery Network (CDN) when a post is merged, not when a post is published.
A fix was implemented on August 26, which uploaded all locally-referenced images to Ghost before sending the post, ensuring a complete URL for each image. However, this fix only affected new posts and did not repair the two existing posts that had been broken since the beginning. Monitoring revealed that both posts returned a 200 status code, despite the missing images.
The issue was that the monitoring was checking the overall page load, not the individual images. A new check was added to extract all images referenced in each published post and request them individually, which immediately found the broken posts. The diagrams are now loading correctly from the CDN, where they should have been all along.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
