You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…las-grekas)
This PR was merged into the 4.4 branch.
Discussion
----------
[HttpClient] Fix Content-Length header when possible
| Q | A
| ------------- | ---
| Branch? | 4.4
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Tickets | Fix#45260
| License | MIT
| Doc PR | -
When userland fails to compute the correct Content-Length header and we can fix it, as is the case in the linked issue.
Commits
-------
f5c2e6e [HttpClient] Fix Content-Length header when possible
Description
See phpro/soap-client#416 for background.
It would be nice if HttpClient calculates a default request content-length header.
I think generally the more http details we provide, the better.
Another option/behavior could be to force re-calculate an existing content-length header as httplug does: https://github.com/php-http/curl-client/blob/2ed4245a817d859dd0c1d51c7078cdb343cf5233/src/Client.php#L346
But perhaps we should produce a log once we change the user value.
Example
No response
The text was updated successfully, but these errors were encountered: