Skip to content

updating strict URL docs #1095

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.

Sign up for GitHub

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

Merged
TomJaeger merged 4 commits into from
Dec 3, 2025
Merged

updating strict URL docs #1095

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
0dc7882
The behavior of strict_urls in the case of page indicators was unclear
robinsowell Dec 3, 2025
953888e
Merge pull request #1093 from ExpressionEngine/strict-urls-clarification
TomJaeger Dec 3, 2025
a998f25
Tweaking for added clarity and because I can't spell.
robinsowell Dec 3, 2025
ee4f790
Merge pull request #1094 from ExpressionEngine/strict-urls-clarification
TomJaeger Dec 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/control-panel/settings/template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,8 @@ If you wish to extend this to the second segment, requiring a valid template, th

Our official recommendation is that users **enable** Strict URLs, as doing so makes the path to your content more precise, allows more relevant 404 pages, and does not allow your content to be shown with variances in the URL structure. However, for legacy reasons, Strict URLs are disabled by default.

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.

### 404 page

This determines which template should be displayed when someone tries to access an invalid URL. If you choose "None", a standard 404 message and server header will be shown.
Expand Down
2 changes: 2 additions & 0 deletions docs/general/system-configuration-overrides.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2987,6 +2987,8 @@ Example Usage:

$config['strict_urls'] = 'n';

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.

**Also found in CP:** `Settings --> Template Settings`: [Enable Strict URLs](control-panel/settings/template.md#enable-strict-urls)

## `template`
Expand Down