Directory

Prevent redirect loops by kkmuffme · Pull Request #6017 · WordPress/wordpress-develop · GitHub
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent redirect loops #6017

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from

Conversation

kkmuffme
Copy link

@kkmuffme kkmuffme commented Feb 2, 2024

Prevent redirect loops when trying to redirect to the current URL, except when changing http to https

It's not possible to create tests for this, since phpunit runs in CLI and PHP will always return null for filter_input in CLI

Trac ticket: https://core.trac.wordpress.org/ticket/60208

Copy link

github-actions bot commented Feb 2, 2024

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 props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props kkmuffme, swissspidy.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Copy link

github-actions bot commented Feb 2, 2024

Test using WordPress Playground

The 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

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@swissspidy swissspidy changed the title Prevent redirect loops https://core.trac.wordpress.org/ticket/60208 Prevent redirect loops Feb 7, 2024
@kkmuffme kkmuffme force-pushed the prevent-redirect-loops branch 6 times, most recently from 7b2c0fe to f010802 Compare March 29, 2024 20:53
}

return $location;
}
endif;

if ( ! function_exists( '_wp_is_self_redirect' ) ) :
Copy link
Member

Choose a reason for hiding this comment

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

Why does this function need to be pluggable?

Copy link
Author

Choose a reason for hiding this comment

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

'cause we're in pluggable.php :-) If you prefer it non-pluggable, that's fine for me, just let me know.

* @param bool $expected true if it should redirect
* @param bool $safe_expected optional expected value of safe_redirect
*/
public function test_wp_redirect_loop( $location, $ssl, $host, $request_uri, $expected, $safe_expected = null ) {
Copy link
Member

Choose a reason for hiding this comment

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

Rather than doing a lot of heavy lifting here, would e2e tests in playwright make more sense?

Copy link
Author

Choose a reason for hiding this comment

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

Possibly, but I don't have experience with playwright (use something else at work) and don't have time to learn that atm.

If there's somebody who can create those, great! Otherwise I don't think that's a blocker, since it has proper tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants