Commit3fc4eee

committed

minor#9165 Added a note about using slashes and the special _format param (javiereguiluz)

This PR was merged into the 2.7 branch.Discussion----------Added a note about using slashes and the special _format paramThis replaces#7973.Commits-------fb9d377 Added a note about using slashes and the special _format param

2 parents2a215c4 +fb9d377 commit3fc4eeeCopy full SHA for 3fc4eee

File tree

1 file changed

-0

lines changed

routing
- slash_in_parameter.rst

1 file changed

-0

lines changed

`‎routing/slash_in_parameter.rst‎`

Lines changed: 9 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -77,6 +77,15 @@ a more permissive regular expression for it:`
`77`	`77`
`78`	`78`	That's it! Now, the ``{token}`` parameter can contain the ``/`` character.
`79`	`79`
	`80`	`+..note::`
	`81`	`+`
	`82`	+ If the route includes the special ``{_format}`` placeholder, you shouldn't
	`83`	+ use the ``.+`` requirement for the parameters that allow slashes. For example,
	`84`	+ if the pattern is ``/share/{token}.{_format}`` and ``{token}`` allows any
	`85`	+ character, the ``/share/foo/bar.json`` URL will consider ``foo/bar.json``
	`86`	`+ as the token and the format will be empty. This can be solved replacing the`
	`87`	+ ``.+`` requirement by ``[^.]+`` to allow any character except dots.
	`88`	`+`
`80`	`89`	`..note::`
`81`	`90`
`82`	`91`	`If the route defines several placeholders and you apply this permissive`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Commit3fc4eee

File tree

1 file changed

1 file changed

`‎routing/slash_in_parameter.rst‎`

0 commit comments