TODO: Allow SAN names in HTTP/2 server push

Suggested-by: Nicolas Grekas
This commit is contained in:
Daniel Stenberg 2019-02-20 08:44:21 +01:00
parent 86cd0cfb90
commit 8bc5ceb204
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2

View File

@ -72,6 +72,7 @@
5.1 Better persistency for HTTP 1.0 5.1 Better persistency for HTTP 1.0
5.2 support FF3 sqlite cookie files 5.2 support FF3 sqlite cookie files
5.3 Rearrange request header order 5.3 Rearrange request header order
5.4 Allow SAN names in HTTP/2 server push
5.5 auth= in URLs 5.5 auth= in URLs
5.6 Refuse "downgrade" redirects 5.6 Refuse "downgrade" redirects
5.7 QUIC 5.7 QUIC
@ -595,6 +596,15 @@
headers use a default value so only headers that need to be moved have to be headers use a default value so only headers that need to be moved have to be
specified. specified.
5.4 Allow SAN names in HTTP/2 server push
curl only allows HTTP/2 push promise if the provided :autority header value
exactly matches the host name given in the URL. It could be extended to allow
any name that would match the Subject Alternative Names in the server's TLS
certificate.
See https://github.com/curl/curl/pull/3581
5.5 auth= in URLs 5.5 auth= in URLs
Add the ability to specify the preferred authentication mechanism to use by Add the ability to specify the preferred authentication mechanism to use by