I support an ancient Zope 2.9 application which I've moved to containers where the ./Dockerfile downloads several tarballs from old.zope.org and installs them into an sufficiently old base image for Zope 2.9 to build and install. Those steps that used to download the tarballs successfully now fail. Specifically, URLs that used to respond with a download now respond with a directory listing. For example:
I assume this is some sort of deployment bug or some such so consider it reported. Also, is there a better, more reliable way to get old zope.org releases?
Ok, we probably shouldn't have been relying on that in the first place.
I thought about trying to build from source (or a GitHub release tag tarball), but I couldn't recall if the old Zope 2 tarball releases were straight out of VCS or if there was any sort of a build step. That was definitely my next fallback though.
This was my bad. old.zope.org has completely moved to a new VM and all that old content is there and available, but the Apache configuration was missing a few rewrite rules.