dotnet / dotnet/aspnetcore

upstream connect error or disconnect/reset before headers. reset reason: protocol error

Open
#43,874 11 comments 0 reactions 0 assignees View on GitHub
area-networking Needs: Attention :wave:
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 5h
Merged PRs (30d)
276

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe the bug

We've launched ASP NET Core 7 Preview app in a Kubernetes cluster with Envoy as a proxy.

When we send `PUT` requests and a response contains a body - we have `502 upstream connect error or disconnect/reset before headers. reset reason: protocol error` for `PUT`. For `GET` it works, for `PUT` without a response body it also works.

After downgrading to `NET 6` it works

### Expected Behavior

Result status code should be 2xx

### Steps To Reproduce

Send a `PUT` HTTP request to an endpoint that returns a result with a body.

### Exceptions (if any)

_No response_

### .NET Version

7.0.0-preview.7.22375.6

### Anything else?

ASP NET Core runtime version: `7.0.0-preview.7.22376.6`
NET Core runtime version: `7.0.0-preview.7.22375.6`

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.