From bf2248ea8527743b569e6727ee12c050f56e5b9c Mon Sep 17 00:00:00 2001 From: davidich Date: Mon, 11 Jun 2018 13:38:31 -0700 Subject: [PATCH] Update route.md (#6826) Remove invalid route example: '/files/myFile.' as the router doesn't match it. --- aspnetcore/fundamentals/routing.md | 1 - 1 file changed, 1 deletion(-) diff --git a/aspnetcore/fundamentals/routing.md b/aspnetcore/fundamentals/routing.md index 474ba39a08..cc32c6b6a0 100644 --- a/aspnetcore/fundamentals/routing.md +++ b/aspnetcore/fundamentals/routing.md @@ -258,7 +258,6 @@ Literal text other than route parameters (for example, `{id}`) and the path sepa URL patterns that attempt to capture a filename with an optional file extension have additional considerations. For example, using the template `files/{filename}.{ext?}` - When both `filename` and `ext` exist, both values will be populated. If only `filename` exists in the URL, the route matches because the trailing period `.` is optional. The following URLs would match this route: * `/files/myFile.txt` -* `/files/myFile.` * `/files/myFile` You can use the `*` character as a prefix to a route parameter to bind to the rest of the URI - this is called a *catch-all* parameter. For example, `blog/{*slug}` would match any URI that started with `/blog` and had any value following it (which would be assigned to the `slug` route value). Catch-all parameters can also match the empty string.