The behavior of strict_urls in the case of page indicators was unclear #1093
Conversation
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
Came up in support as confusing and I'd agree.
TomJaeger
approved these changes
Dec 3, 2025
PDXMan1
reviewed
Dec 3, 2025
There was a problem hiding this comment.
The exception only applies to an uppercase letter “P”, it doesn’t apply to the lowercase letter “p”. So perhaps the wording could be:
NOTE: Note: The pagination indicator, upper-case P# is considered a valid first segment and will not trigger a 404 in order to allow pagination on the index page. Thus https://example.com/P5 will not trigger a 404 with strict_urls enabled.
Contributor
There was a problem hiding this comment.
Great call out... @robinsowell updated in #1094
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Came up in support as confusing and I'd agree.