Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-22326

Redirect .asc and .sha512 links from downloads.a.o to archive.a.o

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: None
    • Component/s: Dists
    • Labels:
      None
    • Project:
      Airflow

      Description

      Following the discussion wit Craig Russel on links to .sha512 .asc files on "downloads.apache.org", I'd love to get .sha512 and .asc URLs redirected from downloads.apache.org to archive.apache.org/dist if they are not found in "downloads".

      Context:

      We have more than 70 packages at Apache Airflow and we release 20-30 of them with monthly cadence.We want to make an installation page that will work properly for our releases and following the rules of announce@apache.org we want to make links to .asc and .sha512 to verify provenence of the packages - the links are supposed to link to "downloads.apache.org" not to mirrors, however the problem is that once we release the "next" version of our software the old packages. signatures, shasums are deleted from downloads and remain only on "archive.apache.org/dist" - which makes old links to downloads.apache.org unusable. This means that every time we release one of the 70 packages we need to find the previous version and regenerate whole documentation (the documentation is generated automatically) for that version just to update 6 links from `downloads` to `archives`.

      I dusted-off a little of my knowledge of Apache web server (used it quite some time ago). I just tested a very simple solution. Assuming "downloads.apache.org" uses Apache Web server - simply adding this rules below will redirect any .asc and .sha512 requests sent to "downloads.apache.org" to corresponding "archives" address, in case the .asc/.sha512 is not found.

      Seems like a super simple solution that could be implemented instantly and all "downloads" links pointing to .asc/sha512 files will be automatically redirected to archives. I think it would be appropriate to have Apache Web Server power to make Apache Projects PMC life a bit easier.

      Maybe it can be done a bit better (I am not an Apache Webserver expert ) - but it seems to me that could be a very simple solution to a complex problem - without side effects really.

      ErrorDocument 404 /dist%{REQUEST_URI}
      RewriteEngine On
      RewriteCond %{REQUEST_URI} ^.*\.asc$ [OR]
      RewriteCond %{REQUEST_URI} ^.*\.sha512$
      RewriteRule ^/dist/ https://archive.apache.org%{REQUEST_URI}

        Attachments

          Activity

            People

            • Assignee:
              humbedooh Daniel Gruno
              Reporter:
              potiuk Jarek Potiuk
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 10m
                10m