-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[HttpClient] Upgrading from version 5.4.3 to version 5.4.5 #46823
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It's a very generic description and it is unlikely to be reproduced by anyone. It could be the server that was temporarily unhealthy or you connection could suffer. Go shopping and ride back to the home and try again. Btw. Why do you update from 5.4.3 to 5.4.5 and not to the 5.4.9? These all are bigfix release so you should upgrade up to the lastes bugfix version for 5.4.* constraint. |
Was in my ticket, so I first did try to update to 5.4.9 and my problem appeared, then I tried to upgrade version one by one to find and the specific version since that bug appered. I'm sure that's not about server or connection performance I had the problem on local dev, preprod server, and production server. Reported by me and other people from different locations. |
Can you profile such a request with for example Blackfire with both versions? Then we could compare the profiles and maybe spot a potential issue. |
Seems that i can't use Blackfire for free ? Unfortunatly 😢 Btw i edited my main post, as I'm sure the error is client sided and not from server as with a request sent from Postman or whatever to the same url I didn't get any performance issues |
yeah, they recently dropped their free plan. |
Can you create a small example application that allows to reproduce your issue? |
@TomLorenzi Do you have something that we could look into? |
I am going to close here for now due to the lack of feedback. Please let us know when you have more information and we can consider to reopen. |
@TomLorenzi if you still have the issue, I would be interested in reading the output of calling |
Sorry for the delay, I didn't get the time to make a small demo project to show it. Next week i'll get the info with debug and i'll post it here @nicolas-grekas |
@nicolas-grekas Sorry for the delay but it seems I have some news First, here is a configuration with 5.4.3 and then 5.4.9 (in my "dist": {
"type": "zip",
"url": "https://api.github.com/repos/symfony/http-client/zipball/a5a467b62dc91eb253db51a91a2c1977f611f60c",
"reference": "a5a467b62dc91eb253db51a91a2c1977f611f60c",
"shasum": ""
}, But this is slow : "dist": {
"type": "zip",
"url": "https://api.github.com/repos/symfony/http-client/zipball/dc0b15e42b762c040761c1eb9ce86a55d47cf672",
"reference": "dc0b15e42b762c040761c1eb9ce86a55d47cf672",
"shasum": ""
}, Here is 5.4.3
With 5.4.9 being slow :
Sorry this may not be the easiest thing to read... |
May i bump this ? |
The diff between both is |
Bug happened with cURL Information => |
Does it happen with more recent versions? |
Should be fixed by #48966. If you have the opportunity, please give it a try and report back. |
…as-grekas) This PR was merged into the 5.4 branch. Discussion ---------- [HttpClient] Let curl handle content-length headers | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #47973, #46499, #46823 | License | MIT | Doc PR | - I'm not sure why (maybe some older and buggy curl versions?) but it looks like curl might send content-length headers to proxies. This didn't happen before #45261 so I'm trying to use curl in the same was as we did by the time, aka letting it handle content-length header when possible. This is something that I already attempted in #45814 but was partly reverted in #45998. The attached patch is free from such issue. Commits ------- 5b27dc2 [HttpClient] Let curl handle content-length headers
Symfony version(s) affected
>5.4.5
Description
I just upraded my symfony/http-client package with composer using
composer require symfony/http-client:5.4.5
(I first upgraded it to 5.4.9 and then I found my performance issue where coming from 5.4.3 to 5.4.5)
Since, I got huge performance issue doing some request, but it didn't seems to apply to every request.
The request I found my performance issues where GET request (can't be sure if it doesn't slow down POST request as well).
How to reproduce
Those request where really simple and here is a code sample :
And when doing
$response->getStatusCode()
it was taking a huge amount of time compared to before my package upgradePossible Solution
Seems the difference between 5.4.3 and 5.4.5 it some default values but I can't tell how it can result in this
Additional Context
Absolutly client sided as the same request send with another tool like Postman didn't get any problems
The text was updated successfully, but these errors were encountered: