Skip to content

docs: update obsolete RFC references in errors and redirects - #2811

Open
vaibhavrvalakunde2006-gif wants to merge 1 commit into
falconry:masterfrom
vaibhavrvalakunde2006-gif:docs/obsolete-rfc-references
Open

vaibhavrvalakunde2006-gif wants to merge 1 commit into
falconry:masterfrom
vaibhavrvalakunde2006-gif:docs/obsolete-rfc-references

Conversation

@vaibhavrvalakunde2006-gif

@vaibhavrvalakunde2006-gif vaibhavrvalakunde2006-gif commented Nov 15, 2026 •

Copy link
Copy Markdown

Summary of Changes
Updates HTTP RFC references in falcon/errors.py and falcon/redirects.py from the obsoleted RFC 7230–7235 to RFC 9110/9111, mapped by status code and section. Docstring-only change; no behavior change.

Related Issues
Refs #2525. Follow-up PRs will cover request.py, response.py, util/ and the docs.

Note: errors.py still references RFC 7238, which may also be obsolete. I left it for maintainers to decide.

Pull Request Checklist

This is just a reminder about the most common mistakes. Please make sure that you tick all appropriate boxes. Reading our contribution guide at least once will save you a few review cycles!

If an item doesn't apply to your pull request, check it anyway to make it apparent that there's nothing to do.

  • Applied changes to both WSGI and ASGI code paths and interfaces (where applicable).
  • Added tests for changed code.
  • Performed automated tests and code quality checks by running tox.
  • Prefixed code comments with GitHub nick and an appropriate prefix.
  • Coding style is consistent with the rest of the framework.
  • Updated documentation for changed code.
    • Added docstrings for any new classes, functions, or modules.
    • Updated docstrings for any modifications to existing code.
    • Updated both WSGI and ASGI docs (where applicable).
    • Added references to new classes, functions, or modules to the relevant RST file under docs/.
    • Updated all relevant supporting documentation files under docs/.
    • A copyright notice is included at the top of any new modules (using your own name or the name of your organization).
    • Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.
  • Changes (and possible deprecations) have towncrier news fragments under docs/_newsfragments/, with the file name format {issue_number}.{fragment_type}.rst. (Run tox -e docs, and inspect docs/_build/html/changes/ in the browser to ensure it renders correctly.)
  • LLM output, if any, has been carefully reviewed and tested by a human developer. (See also: Use of LLMs ("AI").)

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!

PR template inspired by the attrs project.

@vytas7 vytas7 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @vaibhavrvalakunde2006-gif!
Could you go through the PR template and check what's relevant?

@codecov

codecov Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (cc39813) to head (9471c2f).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #2811   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           64        64           
  Lines         8121      8121           
  Branches      1131      1131           
=========================================
  Hits          8121      8121           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants