Cleaning up EOL releases

[Eric]

On Tuesday, February 10th, 2026 at 13:20, Baptiste Jonglez <baptiste at bitsofnetworks.org> wrote:

> > The .overview.json file is there, well-formed and accessible, it's just that access is
> > blocked by the CORS issue...
> 
> I think this is broken since we started redirecting traffic to the archive
> server (in early January), because it doesn't send the CORS headers.
> 
> I've just added the needed CORS headers directly via the CDN, so that we
> don't depend on whether the origin server is setting them correctly or
> not.  If at some point we start directing traffic to tier-1 mirrors, we
> would likely get the same issue.

Hi Baptiste,

I just tested the Firmware Selector and all is good now, no more
CORS errors that I can detect.  I'll chase down the people who were
reporting this and see how they fare.

Thanks,
Eric