You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 14, 2018. It is now read-only.
If you hit /Foo/ on ASP.NET MVC 5, it outputs "Path: default". However, ASP.NET 5 + MVC 6 outputs "NULL". Hitting /Foo/Bar correctly displays "Path: Bar" on both versions. This is the same if you change the default to an empty string - ASP.NET MVC 5 returns "EMPTY" whereas MVC 6 returns "NULL".
I also tried [Route("Foo/{*path=default}")] which did not work either.
Wasn't sure whether to report this in the Routing repo or here; I've reported it here since I think catchall segments are an MVC thing (and also RouteAttribute is an MVC thing)
The text was updated successfully, but these errors were encountered:
I'm wondering if the route value provider is missing a null-or-empty check. My understanding is that a catch-all segment will always have a value, even if it's the empty string.
If you hit
/Foo/
on ASP.NET MVC 5, it outputs "Path: default". However, ASP.NET 5 + MVC 6 outputs "NULL". Hitting/Foo/Bar
correctly displays "Path: Bar" on both versions. This is the same if you change the default to an empty string - ASP.NET MVC 5 returns "EMPTY" whereas MVC 6 returns "NULL".I also tried
[Route("Foo/{*path=default}")]
which did not work either.Wasn't sure whether to report this in the Routing repo or here; I've reported it here since I think catchall segments are an MVC thing (and also
RouteAttribute
is an MVC thing)The text was updated successfully, but these errors were encountered: