Application Passwords: Allow HTTP loopback redirect URLs#11339
Application Passwords: Allow HTTP loopback redirect URLs#11339pento wants to merge 2 commits intoWordPress:trunkfrom
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
This change allows HTTP redirect URLs for loopback addresses (
127.0.0.1,[::1]) inwp_is_authorize_application_redirect_url_valid(), regardless of environment type. This aligns with RFC 8252 7.3.It's worth noting that section 8.3 of the RFC recommends against allowing
localhostas a loopback redirect, since it may be susceptible to firewall interception and DNS resolution poisoning.Trac ticket: https://core.trac.wordpress.org/ticket/57809
Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Opus 4.6
Used for: Initial creation of new tests.
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.