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
The text was updated successfully, but these errors were encountered:
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
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.
Is there an existing issue for this?
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
Screenshots or Videos
No response
Environment Information
Additional Context?
No response
The text was updated successfully, but these errors were encountered: