You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In ASP.NET Core Web API, I can have an empty route on a controller that resolves when using the root url. When using Azure Function HttpTrigger, an empty route is currently impossible, even when using the ASP.NET Core Integration, and when disabling the home page.
Why is this behavior so different?
I should be able to have empty routes on an HttpTrigger.
The text was updated successfully, but these errors were encountered:
In ASP.NET Core Web API, I can have an empty route on a controller that resolves when using the root url. When using Azure Function HttpTrigger, an empty route is currently impossible, even when using the ASP.NET Core Integration, and when disabling the home page.
Why is this behavior so different?
I should be able to have empty routes on an HttpTrigger.
The text was updated successfully, but these errors were encountered: