Skip to content

Broken URLs to apache.org downloads in airflow-ctl installing-from-sources docs (404) #67025

Description

@RamyDerouiche

Under which category would you file this issue?

Airflow Core

Apache Airflow version

main / apache-airflow-ctl 0.1.4 (docs)

What happened and how to reproduce it?

Issue Description

The documentation page for installing airflow-ctl from sources contains two URLs that point to https://downloads.apache.org/airflowctl/.... This path does not exist on Apache's download server — the URLs return HTTP 404.

Four other installing-from-sources.rst files in this same repository already use the correct path pattern https://downloads.apache.org/airflow/..., so the airflow-ctl page is inconsistent with the rest of the project.

Page affected: https://airflow.apache.org/docs/apache-airflow-ctl/stable/installation/installing-from-sources.html

Source file: airflow-ctl/docs/installation/installing-from-sources.rst

Broken URL 1 — "PGP signatures KEYS" link (Release integrity section, line 55)

Current:

`PGP signatures KEYS <https://downloads.apache.org/airflowctl/KEYS>`__

Clicking this link on the rendered docs page returns:

Not Found
The requested URL was not found on this server.

Broken URL 2 — Example bash script (Verifying PyPI releases section)

Current:

curl "https://downloads.apache.org/airflowctl/${airflowctl_version}/apache_airflow_ctl-${airflowctl_version}-py3-none-any.whl.asc" \

The host path downloads.apache.org/airflowctl/${version}/... does not exist. The same page already correctly uses https://downloads.apache.org/airflow/airflow-ctl/0.1.4/... for the direct download links above (sdist / whl / source .asc / .sha512), so the bash example is inconsistent within the same file.

Steps to reproduce

  1. Open https://airflow.apache.org/docs/apache-airflow-ctl/stable/installation/installing-from-sources.html
  2. Scroll to the Release integrity section.
  3. Click the link PGP signatures KEYS → observe the 404 page returned by downloads.apache.org.
  4. Scroll to the Verifying PyPI releases section. The curl command in the example bash script points to the same non-existent host path.

What you think should happen instead?

Both URLs should be updated to use the correct path structure on downloads.apache.org.

Broken URL 1 should become:

`PGP signatures KEYS <https://downloads.apache.org/airflow/KEYS>`__

This is already the URL used by every other installing-from-sources.rst in the project:

  • airflow-core/docs/installation/installing-from-sources.rst (line 59)
  • chart/docs/installing-helm-chart-from-sources.rst (line 51)
  • devel-common/src/sphinx_exts/includes/installing-providers-from-sources.rst (line 57)
  • providers-summary-docs/installing-from-sources.rst (line 52)

Broken URL 2 should follow the existing convention used by the direct download links on the same page:

curl "https://downloads.apache.org/airflow/airflow-ctl/${airflowctl_version}/apache_airflow_ctl-${airflowctl_version}-py3-none-any.whl.asc" \

After the fix, the PGP KEYS link should resolve, and the bash example should successfully download the .asc signature file when run.

Operating System

Not Applicable (docs/web link issue, reproducible from any browser)

Deployment

Other

Apache Airflow Provider(s)

No response

Versions of Apache Airflow Providers

Not Applicable

Official Helm Chart version

Not Applicable

Kubernetes Version

Not Applicable

Helm Chart configuration

Not Applicable

Docker Image customizations

Not Applicable

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions