HTTP3 is now already in full progress
Downgrade redirects can be achived almost exactly like that by setting
CURLOPT_REDIR_PROTOCOLS.
serve as a guideline for others for information, feedback and possible
participation.
-HTTP/3
-------
-
- See the [QUIC and HTTP/3 wiki page](https://github.com/curl/curl/wiki/QUIC).
-
ESNI (Encrypted SNI)
--------------------
Complete and merge [the existing PR](https://github.com/curl/curl/pull/2682).
-Option to refuse HTTPS => HTTP redirects
-----------------------------------------
-
-Possibly as a new bit to `CURLOPT_FOLLOWLOCATION` ?
-
Option to let CURLOPT_CUSTOMREQUEST be overridden on redirect
-------------------------------------------------------------
5.3 Rearrange request header order
5.4 Allow SAN names in HTTP/2 server push
5.5 auth= in URLs
- 5.6 Refuse "downgrade" redirects
5.7 QUIC
6. TELNET
Additionally this should be implemented for proxy base URLs as well.
-5.6 Refuse "downgrade" redirects
-
- See https://github.com/curl/curl/issues/226
-
- Consider a way to tell curl to refuse to "downgrade" protocol with a redirect
- and/or possibly a bit that refuses redirect to change protocol completely.
-
5.7 QUIC
The standardization process of QUIC has been taken to the IETF and can be