ASP.NET Core MVC: Problem with routing argument that contains %2F (forward slash)
I have the following routing attribute in place:
[HttpGet("id/foo")]
My id is a base64 encoded value, and, as such, may contain a forward slash. I'm encoding this forward slash using %2F, however, it seems like ASP.NET Core MVC decodes the URL, then matches routes, as I'm getting a 404 if my id contains %2F.
Is there any way I can allow %2F in my id?
I know there are some answers out there (e.g. How to match web api 2 route with forward slashes in request parameters?), but with all of them, the parameter in question, is always the last, and only then you can use a wildcard (?).
asp.net-mvc asp.net-core asp.net-mvc-routing
asked Nov 10 '18 at 15:58
HelloWorldHelloWorld
8091121
add a comment |
I have the following routing attribute in place:
[HttpGet("id/foo")]
My id is a base64 encoded value, and, as such, may contain a forward slash. I'm encoding this forward slash using %2F, however, it seems like ASP.NET Core MVC decodes the URL, then matches routes, as I'm getting a 404 if my id contains %2F.
Is there any way I can allow %2F in my id?
I know there are some answers out there (e.g. How to match web api 2 route with forward slashes in request parameters?), but with all of them, the parameter in question, is always the last, and only then you can use a wildcard (?).
asp.net-mvc asp.net-core asp.net-mvc-routing
asked Nov 10 '18 at 15:58
HelloWorldHelloWorld
8091121
Maybe dare to try ASP.NET Core 2.2-preview3? See ASP.NET Core 2.2-preview3 blog in the Routing section for the newslugifyroutes. Not sure it works for incoming routes, but will for sure work with Url generation
– Tseng
Nov 10 '18 at 16:19
1
Sorry, wrong article. It's ASP.NET Core 2.2-preview1 about the new Endpoint Routing, look down to "New round-tripping route parameter syntax".
– Tseng
Nov 10 '18 at 16:23
add a comment |
I have the following routing attribute in place:
[HttpGet("id/foo")]
My id is a base64 encoded value, and, as such, may contain a forward slash. I'm encoding this forward slash using %2F, however, it seems like ASP.NET Core MVC decodes the URL, then matches routes, as I'm getting a 404 if my id contains %2F.
Is there any way I can allow %2F in my id?
I know there are some answers out there (e.g. How to match web api 2 route with forward slashes in request parameters?), but with all of them, the parameter in question, is always the last, and only then you can use a wildcard (?).
asp.net-mvc asp.net-core asp.net-mvc-routing
asked Nov 10 '18 at 15:58
HelloWorldHelloWorld
8091121
I have the following routing attribute in place:
[HttpGet("id/foo")]
My id is a base64 encoded value, and, as such, may contain a forward slash. I'm encoding this forward slash using %2F, however, it seems like ASP.NET Core MVC decodes the URL, then matches routes, as I'm getting a 404 if my id contains %2F.
Is there any way I can allow %2F in my id?
I know there are some answers out there (e.g. How to match web api 2 route with forward slashes in request parameters?), but with all of them, the parameter in question, is always the last, and only then you can use a wildcard (?).
asp.net-mvc asp.net-core asp.net-mvc-routing
asp.net-mvc asp.net-core asp.net-mvc-routing
asked Nov 10 '18 at 15:58
HelloWorldHelloWorld
8091121
asked Nov 10 '18 at 15:58
HelloWorldHelloWorld
8091121
edited Nov 10 '18 at 16:07
HelloWorld
asked Nov 10 '18 at 15:58
HelloWorldHelloWorld
8091121
asked Nov 10 '18 at 15:58
HelloWorldHelloWorld
8091121
asked Nov 10 '18 at 15:58
HelloWorldHelloWorld
8091121
8091121
Maybe dare to try ASP.NET Core 2.2-preview3? See ASP.NET Core 2.2-preview3 blog in the Routing section for the newslugifyroutes. Not sure it works for incoming routes, but will for sure work with Url generation
– Tseng
Nov 10 '18 at 16:19
1
Sorry, wrong article. It's ASP.NET Core 2.2-preview1 about the new Endpoint Routing, look down to "New round-tripping route parameter syntax".
– Tseng
Nov 10 '18 at 16:23
add a comment |
Maybe dare to try ASP.NET Core 2.2-preview3? See ASP.NET Core 2.2-preview3 blog in the Routing section for the newslugifyroutes. Not sure it works for incoming routes, but will for sure work with Url generation
– Tseng
Nov 10 '18 at 16:19
1
Sorry, wrong article. It's ASP.NET Core 2.2-preview1 about the new Endpoint Routing, look down to "New round-tripping route parameter syntax".
– Tseng
Nov 10 '18 at 16:23
Maybe dare to try ASP.NET Core 2.2-preview3? See ASP.NET Core 2.2-preview3 blog in the Routing section for the new
slugify routes. Not sure it works for incoming routes, but will for sure work with Url generation– Tseng
Nov 10 '18 at 16:19
Maybe dare to try ASP.NET Core 2.2-preview3? See ASP.NET Core 2.2-preview3 blog in the Routing section for the new
slugify routes. Not sure it works for incoming routes, but will for sure work with Url generation– Tseng
Nov 10 '18 at 16:19
1
1
Sorry, wrong article. It's ASP.NET Core 2.2-preview1 about the new Endpoint Routing, look down to "New round-tripping route parameter syntax".
– Tseng
Nov 10 '18 at 16:23
Sorry, wrong article. It's ASP.NET Core 2.2-preview1 about the new Endpoint Routing, look down to "New round-tripping route parameter syntax".
– Tseng
Nov 10 '18 at 16:23
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53240716%2fasp-net-core-mvc-problem-with-routing-argument-that-contains-2f-forward-slash%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53240716%2fasp-net-core-mvc-problem-with-routing-argument-that-contains-2f-forward-slash%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Maybe dare to try ASP.NET Core 2.2-preview3? See ASP.NET Core 2.2-preview3 blog in the Routing section for the new
slugifyroutes. Not sure it works for incoming routes, but will for sure work with Url generation– Tseng
Nov 10 '18 at 16:19
1
Sorry, wrong article. It's ASP.NET Core 2.2-preview1 about the new Endpoint Routing, look down to "New round-tripping route parameter syntax".
– Tseng
Nov 10 '18 at 16:23