From: Daniel Stenberg Date: Fri, 25 Feb 2022 10:33:29 +0000 (+0100) Subject: TODO: remove "hardcode the "localhost" addresses" X-Git-Tag: curl-7_82_0~17 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=97b3d83ad5ac32661bae2da14a83fac3bd7190fe;p=thirdparty%2Fcurl.git TODO: remove "hardcode the "localhost" addresses" This is implmented since 1a0ebf6632f88 --- diff --git a/docs/TODO b/docs/TODO index 9df8211549..dd1a721035 100644 --- a/docs/TODO +++ b/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