This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 4%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EML%3C/text%3E%3C/svg%3E)
I'm having issues deploying Blazor WASM to Azure App Services. Even if I just take the Blazor default template and try to deploy it, it errors when I go to the Fetch data page with this error: enter image description here
Probably because the content-type is: text\html and not 'application/json; charset=utf-8' like when I run it from with VS, which runs fine. Any suggestion on what is going on and how to correct this? Thanks
@Michael Lambert seems like WeatherForecast is a new route you added to the default Hello World blazor WASM project. Can you provide a snippet of that method?
Actually I just created a new template project and uploaded into a Azure App without any modification. Though I just noticed something strange. It seems to only happen if I try to access it in the browser (any browser) that is launch when VS finishes publishing the App. If I open a different browser (a different tab on the same browser still gives the error) or use a different computer I can access with not issues... Very strange!
What route are you attempting to browse to @Michael Lambert ? Upon publishing your app from VS, you should navigate to the home page...in my case https://ryhill-defaultblazor.azurewebsites.net/. /WeatherForecast isn't a configured route in the default project template, but /fetchdata is and shows the forecast data on the page.
@Michael Lambert I wasn't able to replicate your issue. WeatherForecast isn't an accessible route on the default Blazor template.
The error message for the invalid route is handled on the App.razor file which is what you should've gotten. Verify your App.razor and also check for any modified @Anonymous directives.