IIIF Image API 2.1 and 3.0 both encourage servers to advertise pre-rendered sizes via the sizes array in info.json. Picking from that list (when available) gives a hard ceiling so the upgrade logic never probes past the master, and avoids cache-busting custom widths. Out of scope for this PR — worth a separate issue.
IIIF Image API 2.1 and 3.0 both encourage servers to advertise pre-rendered sizes via the sizes array in info.json. Picking from that list (when available) gives a hard ceiling so the upgrade logic never probes past the master, and avoids cache-busting custom widths. Out of scope for this PR — worth a separate issue.