mirror of
https://github.com/curl/curl.git
synced 2025-03-01 15:15:34 +08:00
TODO: remove "hardcode the "localhost" addresses"
This is implmented since 1a0ebf6632
This commit is contained in:
parent
277256c84d
commit
97b3d83ad5
13
docs/TODO
13
docs/TODO
@ -40,7 +40,6 @@
|
||||
1.22 CURLINFO_PAUSE_STATE
|
||||
1.23 Offer API to flush the connection pool
|
||||
1.25 Expose tried IP addresses that failed
|
||||
1.27 hardcode the "localhost" addresses
|
||||
1.28 FD_CLOEXEC
|
||||
1.29 Upgrade to websockets
|
||||
1.30 config file parsing
|
||||
@ -382,18 +381,6 @@
|
||||
|
||||
https://github.com/curl/curl/issues/2126
|
||||
|
||||
1.27 hardcode the "localhost" addresses
|
||||
|
||||
There's this new spec getting adopted that says "localhost" should always and
|
||||
unconditionally be a local address and not get resolved by a DNS server. A
|
||||
fine way for curl to fix this would be to simply hard-code the response to
|
||||
127.0.0.1 and/or ::1 (depending on what IP versions that are requested). This
|
||||
is what the browsers probably will do with this hostname.
|
||||
|
||||
https://bugzilla.mozilla.org/show_bug.cgi?id=1220810
|
||||
|
||||
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-let-localhost-be-localhost-02
|
||||
|
||||
1.28 FD_CLOEXEC
|
||||
|
||||
It sets the close-on-exec flag for the file descriptor, which causes the file
|
||||
|
Loading…
Reference in New Issue
Block a user