-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Using the NoPrivateNetworkHttpClient results in odd error-message without IP #59021
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
@nicolas-grekas could be related to #59013 but not sure |
Definitely. example.com makes me think this might be related to some handling of RFC6761 |
The problem seems to be related to requests that first encounter a redirect (301) and then run into an error (4xx). Edit: Looks like it also happens when the end-result is a 200... |
The |
I have a reproducible case available at https://gitlab.com/heiglandreas/symfony-http-client-issue-59021 The README contains the error-message including the |
Thanks, fix at #59023 |
…etworkHttpClient (nicolas-grekas) This PR was merged into the 5.4 branch. Discussion ---------- [HttpClient] Fix streaming and redirecting with NoPrivateNetworkHttpClient | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Issues | #59021 | License | MIT Commits ------- 1defdba [HttpClient] Fix streaming and redirecting with NoPrivateNetworkHttpClient
Symfony version(s) affected
7.1.9
Description
We updated recently from http-client 7.1.8 to 7.1.9 and suddenly got a lot of errors like
All triggered in vendor/symfony/http-client/NoPrivateNetworkHttpClient.php:249
The stack trace ends in
From what I understand it looks like the field
primary_ip
is empty and therefore considered not a valid IP-address at all (which makes sense).As this worked in version 7.1.8 (to which we reverted and the errors stopped immediately) it looks like something broke in the latest version.
How to reproduce
See https://gitlab.com/heiglandreas/symfony-http-client-issue-59021
Possible Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: