Skip to content

[5.7] Document encoded forward slashes #4785

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 2 commits into from
Nov 27, 2018
Merged

[5.7] Document encoded forward slashes #4785

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c2ec2d9
Document encoded forward slashes
driesvints Nov 26, 2018
3942e8f
Add note about last route segment
driesvints Nov 26, 2018
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
13 changes: 13 additions & 0 deletions routing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,19 @@ Once the pattern has been defined, it is automatically applied to all routes usi
// Only executed if {id} is numeric...
});

<a name="parameters-encoded-forward-slashes"></a>
#### Encoded Forward Slashes

By default, the Laravel routing component allows all characters except `/`. You must explicitly allow `/` to be part of your placeholder by specifying it with a `where` condition:

Route::get('search/{search}', function ($search) {
return $search;
})->where('search', '.*');

Now when you submit a search with an encoded forward slash, it'll be decoded in the `$search` parameter.

> {note} Please note that using encoded forward slashes is only possible for the last route segment.

<a name="named-routes"></a>
## Named Routes

Expand Down