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

When i requested to 'localhost' host, the Postman sends SYN to IPv6, and then connects to IPv4. #10221

Closed
1 task done
heli-os opened this issue Aug 14, 2021 · 3 comments
Closed
1 task done

Comments

@heli-os
Copy link

heli-os commented Aug 14, 2021

Is there an existing issue for this?

  • I have searched the existing issues

Describe the Issue

When I send a requested to 'localhost' host, it attempts to connect without having a Request Header in IPv6 (probably SYN).

Why is it working like this? Isn't it common to send either IPv4 or IPv6 requests?

If [::1] is a host, it is normal (including request headers).
If 127.0.0.1 is a host, it is normal (including request headers).

Steps To Reproduce

  1. Open the Postman App
  2. Set up Request
  3. Send a Request

Screenshots or Videos

No response

Environment Information

- Operating System: MacOS 11.4
- Platform Type: Native App
- Postman Version: 8.10.0

Additional Context?

No response

@heli-os heli-os changed the title ipv6 behaves strangely when requested to 'localhost' host. When i requested to 'localhost' host, the Postman sends SYN to IPv6, and then connects to IPv4. Aug 14, 2021
@DannyDainton
Copy link
Contributor

Closing due to age and inactivity. If this is still an issue you're facing in the latest version of the platform, we can look at reopening this again.

@montdidier
Copy link

The reason this happens is because localhost exists in both ipv6 (as ::1) and ipv4 (as 127.0.0.1). It checks first to see if an ipv6 connection is available as RFC 3484 states
prefer ipv6 over ipv4 if both resolve and system supports ipv6. This is done with a connection check.

@heli-os
Copy link
Author

heli-os commented May 11, 2023

@montdidier OMG! Thank you for your comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants