Skip to content

Commit 6f5ed1d

Browse files
authored
Merge pull request #1095 from ExpressionEngine/7.dev
updating strict URL docs
2 parents f0692e2 + ee4f790 commit 6f5ed1d

File tree

2 files changed

+4
-0
lines changed

2 files changed

+4
-0
lines changed

docs/control-panel/settings/template.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,8 @@ If you wish to extend this to the second segment, requiring a valid template, th
2525

2626
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.
2727

28+
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.
29+
2830
### 404 page
2931

3032
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.

docs/general/system-configuration-overrides.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2987,6 +2987,8 @@ Example Usage:
29872987

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

2990+
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.
2991+
29902992
**Also found in CP:** `Settings --> Template Settings`: [Enable Strict URLs](control-panel/settings/template.md#enable-strict-urls)
29912993

29922994
## `template`

0 commit comments

Comments
 (0)