Blazor App not direct routing

Question

Blazor App not direct routing

Muneeb Akhter 0

I updated my routes and staticwebapp.config.json to allow routes to get handled by blazor:

"routes": [
    {
      "route": "/api/*",
      "allowedRoles": ["anonymous"]
    },
    {
      "route": "/*",
      "serve": "/index.html",
      "statusCode": 200
    }
  ],
  "navigationFallback": {
    "rewrite": "/index.html"
  },

What is happening. I can click on the nav link that browses me to https://mywebsite.com/login but when i type https://mywebsite.com/login into my browser i get a 404 error

This is causing a lot of issues when routing out and back to the site for verifying emails and making purchases. please help.

Vimal Lalani 170 Reputation points Microsoft External Staff Moderator

2025-08-05T08:27:00.6933333+00:00
Hi Muneeb Akhter

Thank you for posting your question on the Microsoft Q&A forum!

From your description, it sounds like you're experiencing a 404 error when navigating directly to a route like https://mywebsite.com/login by typing it into the browser, even though navigation through your Blazor app’s links works correctly. This issue often relates to how Azure Static Web Apps handles route fallback for single-page applications.

You've already configured the navigationFallback and routing in staticwebapp.config.json, which is the correct approach.

However, to better assist you, could you please check and confirm a few things:

Are there any errors showing up in the browser’s Developer Tools (Console or Network tab) when you directly access the /login URL?

Can you confirm the structure of your project and the exact location of your staticwebapp.config.json file? It should be placed in the root of the app artifact folder (typically wwwroot for Blazor apps).

I tested the same link using different browsers and incognito mode and was able to load content of the website. In some cases, the changes took a bit of time to reflect properly after deployment.

Could you try clearing cache or testing again in incognito/private mode to see if the issue still persists?

Reference: Configure Azure Static Web Apps | Microsoft Learn

Feel free to post back if you have more questions or need help with the workaround.

Your answer

Vimal Lalani 170 Reputation points Microsoft External Staff Moderator

2025-08-05T08:27:00.6933333+00:00

Hi Muneeb Akhter

Thank you for posting your question on the Microsoft Q&A forum!

From your description, it sounds like you're experiencing a 404 error when navigating directly to a route like https://mywebsite.com/login by typing it into the browser, even though navigation through your Blazor app’s links works correctly. This issue often relates to how Azure Static Web Apps handles route fallback for single-page applications.

You've already configured the navigationFallback and routing in staticwebapp.config.json, which is the correct approach.

However, to better assist you, could you please check and confirm a few things:

Are there any errors showing up in the browser’s Developer Tools (Console or Network tab) when you directly access the /login URL?

Can you confirm the structure of your project and the exact location of your staticwebapp.config.json file? It should be placed in the root of the app artifact folder (typically wwwroot for Blazor apps).

I tested the same link using different browsers and incognito mode and was able to load content of the website. In some cases, the changes took a bit of time to reflect properly after deployment.

Could you try clearing cache or testing again in incognito/private mode to see if the issue still persists?

Reference: Configure Azure Static Web Apps | Microsoft Learn

Feel free to post back if you have more questions or need help with the workaround.

Share via

Blazor App not direct routing

Your answer