Closed
Conversation
Redirections problems on wp-admin without this one
Member
|
Is this about multisite installs? |
Author
|
I'll ask previous me from 2023, current me doesn't remember |
Author
The project I was working on at that time wasn't a multisite, so I'd say no. |
Member
|
Happy to revisit if anyone else runs into this, but we haven't seen any reported issues beyond this PR The proposed rewrite changes also look specific to a multisite setup (which isn't currently covered in this doc, would need a new section like Nginx does) Given limited Apache usage in the community, I'm going to close this out for now |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Without this rule, every request to /wp-(content|admin|includes) gives a 404.
If I'm not missing anything, this should be the basic configuration