Score:0

Can I expose a public endpoint from an Azure Static Web App API?

gh flag

I am building a static web application (using Blazor) which includes a Azure Function (C#) API. This is specified when creating the the static app on the portal and is built with GitHub Actions.

In the client code I access the api with HttpClient.GetAsync($"api/{route}") where route is the function Route parameter. This all works fine!

But can I expose a public endpoint to some of the API functions. The URL /api/route returns a message from the client (Blazor) app, saying nothing is found at that location, which I can see is the result of the client app's routing.

Is this possible?

I am on .Net 7 and using Azure functions 4 (Isolated)

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.