gh-145305: Update ocert.org URLs in docs from http to https#145304
gh-145305: Update ocert.org URLs in docs from http to https#145304hugovk merged 1 commit intopython:mainfrom
Conversation
Fixes python#145295. The ocert.org domain now requires HTTPS. Updated all references in documentation to use the secure protocol.
hugovk
left a comment
There was a problem hiding this comment.
Thanks, please prefix the PR title with the issue reference.
And for next time, we usually don't issues for fixes like this.
|
This is a duplicate of a PR opened shortly before: #145295 ? |
|
The joys of LLM-driven PRs, I've seen and heard of many projects getting duplicate PRs in the past few days... It's getting pretty tiring. Anyway, this PR wins because the CLA is signed. |
…thonGH-145304) (cherry picked from commit 11eec7a492670fff67fc083036d595f8498217db) Co-authored-by: indoor47 <indoor47@gmail.com> Co-authored-by: Adam (indoor47) <adamai@agentmail.to>
…thonGH-145304) (cherry picked from commit 11eec7a) Co-authored-by: indoor47 <indoor47@gmail.com> Co-authored-by: Adam (indoor47) <adamai@agentmail.to>
|
GH-145322 is a backport of this pull request to the 3.14 branch. |
|
GH-145323 is a backport of this pull request to the 3.13 branch. |
|
Ha, the backports also need the CLA signed for another email. @indoor47 Please could you sign the CLA with your gmail address? See https://devguide.python.org/getting-started/pull-request-lifecycle/#why-do-i-need-to-sign-the-cla-again and #145322 (comment). |
Moreover: I've seen commits from old merged PRs from repo maintainers re-submitted and other PRs with "Fixes #some_merged_pr" but containing nothing useful. |
gh-issue-145305: update ocert.org URLs from http to https
Summary
Two references to
http://ocert.orgin the documentation now usehttps://instead. The site supports HTTPS and these are long-lived documentation links that should use the secure scheme.Changes
Doc/reference/datamodel.rst: updated ocert.org advisory link to HTTPSDoc/using/cmdline.rst: updated the same advisory link to HTTPS (hash randomization docs)Motivation
Both occurrences reference the same
ocert-2011-003advisory about hash-flooding denial-of-service, used to explain-R/PYTHONHASHSEED. The current HTTP URL results in a redirect; using HTTPS directly is more correct and avoids the redirect.Closes #145305