Should + (plus) sign work for Routes in Azure Functions 2

We have migrated an app to Azure Functions 2, and we have the following route setup:

"testABC/testA/testB"

in the azure function code we have:

public static HttpResponseMessage Run(HttpRequestMessage req, string testA, string testB, TraceWriter log)

 var res = req.CreateResponse(HttpStatusCode.OK);
 res.Content = new StringContent($"testA - testB");
 return res;

When I run this url: https://xxx.azurewebsites.net/testABC/74aff65f-5f46-4e28-838b-3093d18a3552/test
it works

However if I add a plus sign it does not work: When I run this url: https://xxx.azurewebsites.net/testABC/74aff65f-5f46-4e28-838b-3093d18a3552/te+st
It gives this error:

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Adding a space instead of a plus works too. This isn't an issue with Azure Functions 1. What am I missing here?

edited Nov 16 '18 at 8:22

Jerry Liu

11.4k11233

asked Nov 15 '18 at 22:31

tank104

79110

By "route setup", do you mean that you are using an Azure Function Proxy? There are also route templates, although then your url would look more like ".net/api/testABC" docs.microsoft.com/en-us/azure/azure-functions/…

– Marie Hoeger
Nov 15 '18 at 23:56

Hi Marie, I am not using any proxies - just the standard Route Template. Its working fine - except when there is a + in the value

– tank104
Nov 16 '18 at 2:06

add a comment |

We have migrated an app to Azure Functions 2, and we have the following route setup:

"testABC/testA/testB"

in the azure function code we have:

public static HttpResponseMessage Run(HttpRequestMessage req, string testA, string testB, TraceWriter log)

 var res = req.CreateResponse(HttpStatusCode.OK);
 res.Content = new StringContent($"testA - testB");
 return res;

When I run this url: https://xxx.azurewebsites.net/testABC/74aff65f-5f46-4e28-838b-3093d18a3552/test
it works

However if I add a plus sign it does not work: When I run this url: https://xxx.azurewebsites.net/testABC/74aff65f-5f46-4e28-838b-3093d18a3552/te+st
It gives this error:

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Adding a space instead of a plus works too. This isn't an issue with Azure Functions 1. What am I missing here?

edited Nov 16 '18 at 8:22

Jerry Liu

11.4k11233

asked Nov 15 '18 at 22:31

tank104

79110

By "route setup", do you mean that you are using an Azure Function Proxy? There are also route templates, although then your url would look more like ".net/api/testABC" docs.microsoft.com/en-us/azure/azure-functions/…

– Marie Hoeger
Nov 15 '18 at 23:56

Hi Marie, I am not using any proxies - just the standard Route Template. Its working fine - except when there is a + in the value

– tank104
Nov 16 '18 at 2:06

add a comment |

We have migrated an app to Azure Functions 2, and we have the following route setup:

"testABC/testA/testB"

in the azure function code we have:

public static HttpResponseMessage Run(HttpRequestMessage req, string testA, string testB, TraceWriter log)

 var res = req.CreateResponse(HttpStatusCode.OK);
 res.Content = new StringContent($"testA - testB");
 return res;

When I run this url: https://xxx.azurewebsites.net/testABC/74aff65f-5f46-4e28-838b-3093d18a3552/test
it works

However if I add a plus sign it does not work: When I run this url: https://xxx.azurewebsites.net/testABC/74aff65f-5f46-4e28-838b-3093d18a3552/te+st
It gives this error:

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Adding a space instead of a plus works too. This isn't an issue with Azure Functions 1. What am I missing here?

edited Nov 16 '18 at 8:22

Jerry Liu

11.4k11233

asked Nov 15 '18 at 22:31

tank104

79110

We have migrated an app to Azure Functions 2, and we have the following route setup:

"testABC/testA/testB"

in the azure function code we have:

public static HttpResponseMessage Run(HttpRequestMessage req, string testA, string testB, TraceWriter log)

 var res = req.CreateResponse(HttpStatusCode.OK);
 res.Content = new StringContent($"testA - testB");
 return res;

When I run this url: https://xxx.azurewebsites.net/testABC/74aff65f-5f46-4e28-838b-3093d18a3552/test
it works

However if I add a plus sign it does not work: When I run this url: https://xxx.azurewebsites.net/testABC/74aff65f-5f46-4e28-838b-3093d18a3552/te+st
It gives this error:

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Adding a space instead of a plus works too. This isn't an issue with Azure Functions 1. What am I missing here?

azure azure-functions

edited Nov 16 '18 at 8:22

Jerry Liu

11.4k11233

asked Nov 15 '18 at 22:31

tank104

79110

edited Nov 16 '18 at 8:22

Jerry Liu

11.4k11233

asked Nov 15 '18 at 22:31

tank104

79110

edited Nov 16 '18 at 8:22

Jerry Liu

11.4k11233

edited Nov 16 '18 at 8:22

Jerry Liu

11.4k11233

edited Nov 16 '18 at 8:22

Jerry Liu

11.4k11233

asked Nov 15 '18 at 22:31

tank104

79110

asked Nov 15 '18 at 22:31

tank104

79110

asked Nov 15 '18 at 22:31

tank104

79110

By "route setup", do you mean that you are using an Azure Function Proxy? There are also route templates, although then your url would look more like ".net/api/testABC" docs.microsoft.com/en-us/azure/azure-functions/…

– Marie Hoeger
Nov 15 '18 at 23:56

Hi Marie, I am not using any proxies - just the standard Route Template. Its working fine - except when there is a + in the value

– tank104
Nov 16 '18 at 2:06

add a comment |

By "route setup", do you mean that you are using an Azure Function Proxy? There are also route templates, although then your url would look more like ".net/api/testABC" docs.microsoft.com/en-us/azure/azure-functions/…

– Marie Hoeger
Nov 15 '18 at 23:56

Hi Marie, I am not using any proxies - just the standard Route Template. Its working fine - except when there is a + in the value

– tank104
Nov 16 '18 at 2:06

By "route setup", do you mean that you are using an Azure Function Proxy? There are also route templates, although then your url would look more like ".net/api/testABC" docs.microsoft.com/en-us/azure/azure-functions/…

– Marie Hoeger
Nov 15 '18 at 23:56

Hi Marie, I am not using any proxies - just the standard Route Template. Its working fine - except when there is a + in the value

– tank104
Nov 16 '18 at 2:06

add a comment |

1 Answer
1

active

oldest

votes

Update

It turns out allowDoubleEscaping="true" missing in v2 . It should have been fixed since runtime 2.0.12265, right now I see 2.0.12275 on my side.

Got same error on my side, but everything works locally so I doubt there could be some server request filter settings on Azure which restrict plus sign. Have opened an issue to track this problem.

edited Jan 21 at 2:19

answered Nov 16 '18 at 8:21

Jerry Liu

11.4k11233

Thanks Jerry - that was going to be my next step; but I just thought that it couldn't be possible that this overlooked and that I was doing something wrong.

– tank104
Nov 18 '18 at 23:28

@tank104 We probably did everything we could. As mentioned in the issue, I can use + in url in v1 on Azure site as you have found, both v1 and v2 work locally as well. The inconsistency should prove that we didn't do anything wrong. It's possible that there are some settings to check but I didn't find any clue in Azure Functions document. So I assume it's time we move to the next step.

– Jerry Liu
Nov 19 '18 at 1:22

Sorry for the delayed response - thanks for fixing!

– tank104
Feb 8 at 11:31

add a comment |

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
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53328792%2fshould-plus-sign-work-for-routes-in-azure-functions-2%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

Update

It turns out allowDoubleEscaping="true" missing in v2 . It should have been fixed since runtime 2.0.12265, right now I see 2.0.12275 on my side.

Got same error on my side, but everything works locally so I doubt there could be some server request filter settings on Azure which restrict plus sign. Have opened an issue to track this problem.

edited Jan 21 at 2:19

answered Nov 16 '18 at 8:21

Jerry Liu

11.4k11233

Thanks Jerry - that was going to be my next step; but I just thought that it couldn't be possible that this overlooked and that I was doing something wrong.

– tank104
Nov 18 '18 at 23:28

@tank104 We probably did everything we could. As mentioned in the issue, I can use + in url in v1 on Azure site as you have found, both v1 and v2 work locally as well. The inconsistency should prove that we didn't do anything wrong. It's possible that there are some settings to check but I didn't find any clue in Azure Functions document. So I assume it's time we move to the next step.

– Jerry Liu
Nov 19 '18 at 1:22

Sorry for the delayed response - thanks for fixing!

– tank104
Feb 8 at 11:31

add a comment |

Update

It turns out allowDoubleEscaping="true" missing in v2 . It should have been fixed since runtime 2.0.12265, right now I see 2.0.12275 on my side.

Got same error on my side, but everything works locally so I doubt there could be some server request filter settings on Azure which restrict plus sign. Have opened an issue to track this problem.

edited Jan 21 at 2:19

answered Nov 16 '18 at 8:21

Jerry Liu

11.4k11233

Thanks Jerry - that was going to be my next step; but I just thought that it couldn't be possible that this overlooked and that I was doing something wrong.

– tank104
Nov 18 '18 at 23:28

@tank104 We probably did everything we could. As mentioned in the issue, I can use + in url in v1 on Azure site as you have found, both v1 and v2 work locally as well. The inconsistency should prove that we didn't do anything wrong. It's possible that there are some settings to check but I didn't find any clue in Azure Functions document. So I assume it's time we move to the next step.

– Jerry Liu
Nov 19 '18 at 1:22

Sorry for the delayed response - thanks for fixing!

– tank104
Feb 8 at 11:31

add a comment |

Update

It turns out allowDoubleEscaping="true" missing in v2 . It should have been fixed since runtime 2.0.12265, right now I see 2.0.12275 on my side.

Got same error on my side, but everything works locally so I doubt there could be some server request filter settings on Azure which restrict plus sign. Have opened an issue to track this problem.

edited Jan 21 at 2:19

answered Nov 16 '18 at 8:21

Jerry Liu

11.4k11233

Update

It turns out allowDoubleEscaping="true" missing in v2 . It should have been fixed since runtime 2.0.12265, right now I see 2.0.12275 on my side.

Got same error on my side, but everything works locally so I doubt there could be some server request filter settings on Azure which restrict plus sign. Have opened an issue to track this problem.

edited Jan 21 at 2:19

answered Nov 16 '18 at 8:21

Jerry Liu

11.4k11233

edited Jan 21 at 2:19

answered Nov 16 '18 at 8:21

Jerry Liu

11.4k11233

answered Nov 16 '18 at 8:21

Jerry Liu

11.4k11233

answered Nov 16 '18 at 8:21

Jerry Liu

11.4k11233

Thanks Jerry - that was going to be my next step; but I just thought that it couldn't be possible that this overlooked and that I was doing something wrong.

– tank104
Nov 18 '18 at 23:28

@tank104 We probably did everything we could. As mentioned in the issue, I can use + in url in v1 on Azure site as you have found, both v1 and v2 work locally as well. The inconsistency should prove that we didn't do anything wrong. It's possible that there are some settings to check but I didn't find any clue in Azure Functions document. So I assume it's time we move to the next step.

– Jerry Liu
Nov 19 '18 at 1:22

Sorry for the delayed response - thanks for fixing!

– tank104
Feb 8 at 11:31

add a comment |

Thanks Jerry - that was going to be my next step; but I just thought that it couldn't be possible that this overlooked and that I was doing something wrong.

– tank104
Nov 18 '18 at 23:28

@tank104 We probably did everything we could. As mentioned in the issue, I can use + in url in v1 on Azure site as you have found, both v1 and v2 work locally as well. The inconsistency should prove that we didn't do anything wrong. It's possible that there are some settings to check but I didn't find any clue in Azure Functions document. So I assume it's time we move to the next step.

– Jerry Liu
Nov 19 '18 at 1:22

Sorry for the delayed response - thanks for fixing!

– tank104
Feb 8 at 11:31

Thanks Jerry - that was going to be my next step; but I just thought that it couldn't be possible that this overlooked and that I was doing something wrong.

– tank104
Nov 18 '18 at 23:28

@tank104 We probably did everything we could. As mentioned in the issue, I can use + in url in v1 on Azure site as you have found, both v1 and v2 work locally as well. The inconsistency should prove that we didn't do anything wrong. It's possible that there are some settings to check but I didn't find any clue in Azure Functions document. So I assume it's time we move to the next step.

– Jerry Liu
Nov 19 '18 at 1:22

Sorry for the delayed response - thanks for fixing!

– tank104
Feb 8 at 11:31

add a comment |

draft saved

draft discarded

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.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Myujth