Replies: 1 comment 7 replies
-
|
Hello @reinux, thanks for opening this discussion. Is this behavior happening when using the Endpoint Routing? |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
ASP.NET routing has RouteOptions.AppendTrailingSlash, which I tried setting but it doesn't seem to do anything:
Ideally, I'd like to set it just for certain endpoints. I'm also not able to just route
footofoo/, because they are considered the same by the router. This seems like somewhat of an oversight by ASP.NET, especially as browser consider<a href="bar.html">to mean something totally different depending on whether the page is/fooor/foo/.In other words, unless I'm missing something, it's always necessary to provide the full path in html. That's less than ideal for composability/maintainability.
What's the correct solution here?
Beta Was this translation helpful? Give feedback.
All reactions