aboutsummaryrefslogtreecommitdiff
path: root/docs/TODO
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2018-01-20 13:57:12 +0100
committerDaniel Stenberg <daniel@haxx.se>2018-01-20 13:57:12 +0100
commitec122c4c83be69a37a56e29377f3d19c02d9c1ca (patch)
tree089951d5a9d768a8224b81aa33a6dc4cc2043851 /docs/TODO
parenta5e6d6ebcb8dc00f264c89c3e5376f042c372efb (diff)
TODO: two possible name resolver improvements
Diffstat (limited to 'docs/TODO')
-rw-r--r--docs/TODO21
1 files changed, 21 insertions, 0 deletions
diff --git a/docs/TODO b/docs/TODO
index 781393169..25f860b42 100644
--- a/docs/TODO
+++ b/docs/TODO
@@ -27,6 +27,8 @@
1.9 Cache negative name resolves
1.10 auto-detect proxy
1.11 minimize dependencies with dynamically loaded modules
+ 1.12 updated DNS server while running
+ 1.13 DNS-over-HTTPS
1.14 Typesafe curl_easy_setopt()
1.15 Monitor connections in the connection pool
1.16 Try to URL encode given URL
@@ -273,6 +275,25 @@
app/invoke/used protocols would be necessary to load. See
https://github.com/curl/curl/issues/349
+1.12 updated DNS server while running
+
+ If /etc/resolv.conf gets updated while a program using libcurl is running, it
+ is may cause name resolves to fail unless res_init() is called. We should
+ consider calling res_init() + retry once unconditionally on all name resolve
+ failures to mitigate against this. Firefox works like that. Note that Windows
+ doesn't have res_init() or an alternative.
+
+ https://github.com/curl/curl/issues/2251
+
+1.13 DNS-over-HTTPS
+
+ By adding support for DNS-over-HTTPS curl could resolve host names using a
+ totally separate name server than the standard system resolver, while at the
+ same time doing so over a communication channel that enhances privacy and
+ security.
+
+ https://github.com/curl/curl/wiki/DNS-over-HTTPS
+
1.14 Typesafe curl_easy_setopt()
One of the most common problems in libcurl using applications is the lack of