Artwork published on http should be stored on https where its host serves it #110
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The page is https and must not load http. #90 made http-only artwork come through /api/art, but artwork whose host also serves https still goes the long way: 622 stored image URLs are http (3 feeds, 619 items), from 5 hosts. Checked 2026-10-02: assets1/assets2.ignimgs.com, www.righto.com and johnsroadtrip.blogspot.com serve the same images on https; cdn.thesecretcabal.com (615 of them) presents another name's certificate, so it stays on /api/art. Wanted: on a scan, try each http artwork host on https once and store https where it works, rewriting that feed's stored items too.
Fixed in
54d827fand38ebc7b: a scan tries each http artwork host on https once per feed, the hosts its body names and those its stored items still name, and stores https where the host answers with an image, rewriting that feed's stored items. In production after refreshing the three affected feeds: john-s-road-trip, ken-shirriff-s-blog and IGN's 5 old items are on https. What remains on http is cdn.thesecretcabal.com (615 rows), whose certificate is for another name; the page loads those through /api/art, so it still loads nothing over http.