For HTTP/1 unary mode, use Content-Length instead of chunk

[finefuture]

What is the purpose of the change

Refer: #13933

For example:

Brief changelog

Verifying this change

Checklist

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Add some description to dubbo-website project if you are requesting to add a feature.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.

[finefuture]

@oxsean PTAL

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 38.54%. Comparing base (a12975a) to head (050d2d0).

Additional details and impacted files

@@            Coverage Diff             @@
##              3.3   #13979      +/-   ##
==========================================
- Coverage   38.55%   38.54%   -0.01%     
==========================================
  Files        1895     1896       +1     
  Lines       79272    79302      +30     
  Branches    11528    11527       -1     
==========================================
+ Hits        30560    30565       +5     
- Misses      44439    44466      +27     
+ Partials     4273     4271       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[AlbumenJ]

For HTTP/2 unary, should we fix it?

[finefuture]

For HTTP/2 unary, should we fix it?

Maybe we don't need to fix it, refer to this link: https://stackoverflow.com/questions/77520309/why-is-content-length-header-not-sent-over-http-3.
@oxsean What do you think?

[oxsean]

@AlbumenJ @finefuture I think END_STREAM flag is enough, because END_STREAM flag is mandatory.

[AlbumenJ]

@oxsean PTAL

[oxsean]

@AlbumenJ LGTM

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud