Skip to content

Fixed the explanation of the utf8 router option #12636

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
merged 1 commit into from
Nov 23, 2019
Merged

Fixed the explanation of the utf8 router option #12636

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 4 additions & 1 deletion reference/configuration/framework.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1152,7 +1152,10 @@ utf8

**type**: ``boolean`` **default**: ``false``

When this option is set to ``true``, route patterns can include UTF-8 characters.
When this option is set to ``true``, the regular expressions used in the
:ref:`requirements of route parameters <routing-requirements>` will match any
UTF-8 character when using ``.``, instead of matching only a single byte.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The u modifier influences a bit more than just the ., doesn't it? IIRC it also changes how the \w class matches for example.


If the charset of your application is UTF-8 (as defined in the
:ref:`getCharset() method <configuration-kernel-charset>` of your kernel) it's
recommended to set it to ``true``. This will make non-UTF8 URLs to generate 404
Expand Down