microsoft / microsoft/aspire

Aspire application deployed to Azure Container App does not communicate over HTTP/2

Open
#4,733 3 comments 4 reactions 0 assignees View on GitHub
area-deployment azure azure-container-apps documentation
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.