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 in there I replaced the images* subdomains with a CDN, but when I upgraded the site to HTTPS, the fact that my CDN couldn't usefully use a HTTP certificate for my own domain name made me bring them back onto a server under my control.
-
-
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
- 3 more replies
New conversation -
-
-
I dunno, nowadays I can throw an entire server AND static image host (S3 bucket, whatever) behind a CDN and have them both wrapped with the same domain name and cert.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.