[release/7.0] Fix RequestBody logging when zero byte read is used

[github-actions]

Backport of #47794 to release/7.0

/cc @BrennanConroy

Fix RequestBody logging when zero byte read is used

Description

In 7.0, zero-byte reads became the default in Kestrel, when using the PipeReader feature, which weren't handled by the HttpLoggingMiddleware. It would treat the zero-byte read as the end of what it should log for the request body, and since zero-byte reads are the first read, nothing would be logged.

Customer Impact

Using the HttpLoggingMiddleware may stop logging request bodies when upgrading from 6.0 to 7.0.

Customer reported issue #47216

Regression?

• Yes
• No

Regressed in 7.0

Risk

• High
• Medium
• Low

Small change and well understood problem.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

[ghost]

Hi @github-actions[bot]. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document.
Otherwise, please add tell-mode label.

[ghost]

Hi @github-actions[bot]. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge.

To learn more about how to prepare a servicing PR click here.

[ghost]

Hi @github-actions[bot]. This PR was just approved to be included in the upcoming servicing release. Somebody from the @dotnet/aspnet-build team will get it merged when the branches are open. Until then, please make sure all the CI checks pass and the PR is reviewed.

[amcasey]

@BrennanConroy Good to go?

[BrennanConroy]

No, you need to wait for servicing branches to open. Usually Will will handle merging then.