#100990Pages with trailing slash in slug are not resolved if requested uri does not contain a trailing slash
Description
Description
The slug field for pages may contain trailing slash or not.
The generator basically creates it without, but it valid to
enter a trailing slash for a slug manually by the editor.
This led to issues and the past and have been addressed by
changes #86055 and #89091.
At a later point default slug resolving for a language if
a valid localized page exists have been solved, reported
with #88715 and #96010.
If a page slug contains a trailing slash, but the request
does not contain a trailing slash, page is not resolved.
For the mentioned changes above some tests have been added,
sadly not covering all possible constellation and therefore
not detecting this case earlier.
Pages falling into this case should be resolved properly and
covered by a couple of additional tests.
Confirmed for:
- TYPO3 11.5.x
- TYPO3 12.4.x
- TYPO3 main
Not working example
page["slug"]......: /my-page/features/ request...........: /my-page/features
is not resolved. The expectation is, that this page is
resolved correctly.
Working examples
page["slug"]......: /my-page/features/ request...........: /my-page/features/
page["slug"]......: /my-page/features request...........: /my-page/features/
page["slug"]......: /my-page/features request...........: /my-page/features
Reviews 3
Related issues 5
- Bug #86055pages.slug always removes the trailing slash
- Bug #88715Wrong routes for default url slugs on translated base path pages
- Bug #89091Page with a slug with trailing slash results in 404
- Bug #96010Translated pages can be loaded with slug of default language
- Bug #96599Slugs with and without trailing slash are considered different but will confuse URL handling in frontend