Static-web-apps: Route containing plus sign '+' returns 404

[shawntoffel]

One of my hugo generated blogs currently hosted in Azure blob storage allows authors to specify their own tags for grouping posts. One of the tags happens to be "A+" which results in a URL such as https://contoso.com/tags/A+/

Hosted via Azure Static Web Apps this URL returns a 404 HTTP status code with content: "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."

Using a URL encoded plus sign "%2B" has the same result.

[miwebst]

Hi @shawntoffel thanks for reporting this! We will take a look and get back to you.

[miwebst]

Hi @shawntoffel we have found the issue and are working on a fix, it will roll out with our next update.

[shawntoffel]

Excellent. Thank you!

[miwebst]

Just an update here, the problem is actually more complex than we originally thought it was. We are still working on a solution to this but it will take more time than our next release. I apologize for the inconvenience!

[araemo]

I think I am running into the same problem. I spotted this in the application logs for my web service (so, I'm not sure if this counts as a static web app, even though I'm only doing static file hosting):

<h3>HTTP Error 404.11 - Not Found</h3><h4>The request filtering module is configured to deny a request that contains a double escape sequence.</h4>

So... I tried to use a web.config to set <requestFiltering allowDoubleEscaping="true" /> as I have seen as fixes to the above message, but that caused my site to stop serving any files with a 500 error instead.

[IT-CASADO]

I'm running into the same problem and didn't find a way to make it work...

[miwebst]

We are about 2 weeks away from having this fixed. I'll update this thread when it is.

[thomastvedt]

We're getting 404 on url's containing @ and #. I guess this could be related? Are there any (temporary) workarounds?

[miwebst]

Do you have an example for the #? I believe this is the same problem for the @

[miwebst]

This should be fixed now for the + case. Thank you for your patience! @thomastvedt can you check if your scenarios are now fixed too?

[thomastvedt]

Example url: https://myapp.azurestaticapps.net/en/path/123/50802202220573Z/[email protected]#0f654e0811aa02651002b92cdc4

routes.json:

  "routes": [
    {
      "route": "/*",
      "serve": "/index.html",
      "statusCode": 200
    }
  ],

This path should be redirected to our SPA, but resulted in 404. I did a quick test now, and this still results in 404 :( I'll test some more tomorrow 👍🏼

Also notice the dot . in my url :)
=> seems like the dot is the bad guy here.. 🐤

[thomastvedt]

Happy new year! 🚀
Any news on this one? 😄

[miwebst]

Hey @thomastvedt,

Happy new year! Sorry for the long delay. We have something in the works that will address this. I will follow-up here when that is public and ready for use!