Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NET Aspire application deployed to Azure Container App does not communicate over HTTP/2 #4733

Open
joseph-hungerman opened this issue Jul 1, 2024 · 0 comments

Comments

@joseph-hungerman
Copy link

I have deployed a .NET8 Aspire solution to ACA. The complete solution consists of 6 projects: prometheus container, grafana container, redis container, Blazor Web App, 2 Web APIs. The 2 web APIS leverage gRPC to communicate. When running the solution locally everything works as expected. After deploying to ACA, the application fails. When I have all of the .NET containers set to a transport of http2, the application will not startup giving a protocol error. When switching the Blazor app to auto, it the protocol error gets pushed down to the first API it calls. If I set every .NET container to auto, I get an error stating that HTTP/1.1 requests are not allowed to a gRPC service. All 3 .NET containers need to handle both http1.1 and http2 requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant