linzch3 opened a new pull request, #77336:
URL: https://github.com/apache/airflow/pull/77336

   Hi, a few external links in the docs are dead, I found them while running a 
quick link check over `airflow-core/docs` and `chart/docs`:
   
   - `howto/run-behind-proxy.rst`: `www.uvicorn.org` doesn't respond anymore, 
Uvicorn's docs moved to `uvicorn.dev` (their README links there now). 
`#proxies-and-forwarded-headers` exists on the new page.
   - `logging-tasks.rst`: `docs.gunicorn.org/en/latest/settings.html` now 
redirects to `gunicorn.org/en/latest/settings.html`, which is a 404. The 
settings page is `gunicorn.org/reference/settings/` now.
   - `chart/docs/service-account-token-examples.rst`: both Kyverno links 
pointed at the same `/policies/other/restrict-sa-automount-sa-token/...` page, 
which is a 404 since Kyverno only lists the ValidatingPolicy version of that 
policy (`other-vpol/...`) on main. I pointed the first one there. The second 
label is "Restrict Auto-Mount of Service Account Tokens", which is actually a 
different (pod-level) policy, `restrict-automount-sa-token`. It's not on 
kyverno.io anymore, so I linked it to the yaml on the `release-1.19` branch of 
kyverno/policies, the last branch that still has it. Happy to just drop that 
second link instead if u prefer.
   
   Only URLs changed, no wording. I checked every new URL returns 200. Didn't 
build the docs locally.
   
   I left the `apache/magpie` links in 
`contributing-docs/25_maintainer_pr_triage.md` alone: they're also 404 since 
magpie renamed `pr-management-triage` to `pr-triage` and split some files, but 
mapping those properly is better done by someone who knows the skill layout.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Opus 5.5 following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to