Self-hosting my own blog has been a joyful experience of, every six months, getting reported that images fail to load on old posts because of a tweak to Nginx configs for the HTTPS site at some point in the arbitrary past. When did we make the Internet so ()#%(& complicated.
At some point, as a weekend project, I upgraded the blog to HTTPS everywhere, but did not test this upgrade on my (relatively rare) posts which contained images in the body.
-
-
Had I done that, I would have realized that request to the HTTPS (but not HTTP) images{1,2,3,4} subdomains were being routed not to the Nginx configuration for the images subdomain but rather to the configuration for the blog, which would (for regex related tomfoolery) instead
-
reply with an HTML document including my blog's archive page. So what I actually needed to do was include an explicit configuration for images{1,2,3,4} on the 443 port to stop Nginx from waterfalling that to a different configuration. Obviously.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.