Skip to content
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

No fallback to IPv4 address when IPv6 connect attempt fails with Network is unreachable: connect #16723

Closed
dkocher opened this issue Dec 26, 2024 Discussed in #16703 · 1 comment · Fixed by #16724
Closed
Assignees
Labels
googledrive Google Drive Protocol Implementation
Milestone

Comments

@dkocher
Copy link
Contributor

dkocher commented Dec 26, 2024

Discussed in #16703.

The issue is that with #16639 IPv6 address may be preferred over IPv4 and no attempt is made to connect using IPv4 if an IPv6 address causes java.net.SocketException) Network is unreachable: connect.

@dkocher dkocher added the googledrive Google Drive Protocol Implementation label Dec 26, 2024
@dkocher dkocher added this to the 9.1.2 milestone Dec 26, 2024
@dkocher dkocher self-assigned this Dec 26, 2024
@dkocher dkocher linked a pull request Dec 26, 2024 that will close this issue
@dkocher
Copy link
Contributor Author

dkocher commented Dec 27, 2024

Referencing upstream issue HTTPCLIENT-2288 1.

Footnotes

  1. https://issues.apache.org/jira/browse/HTTPCLIENT-2288

dkocher added a commit that referenced this issue Dec 27, 2024
…ketException` and retry with next resolved address. Fix #16723.
dkocher added a commit that referenced this issue Dec 29, 2024
Always sort result set from DNS resolver
@dkocher dkocher changed the title No fallback to IPv4 adress when IPv6 connect attempt fails with Network is unreachable: connect No fallback to IPv4 address when IPv6 connect attempt fails with Network is unreachable: connect Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
googledrive Google Drive Protocol Implementation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant