Skip to content

Commit

Permalink
Make HTTPSSVC imply fatal certificate errors
Browse files Browse the repository at this point in the history
This is the other half of HSTS. Closes MikeBishop#87.
  • Loading branch information
davidben committed Dec 16, 2019
1 parent 9c133e8 commit 26e93ec
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions draft-ietf-dnsop-svcb-httpssvc.md
Original file line number Diff line number Diff line change
Expand Up @@ -918,6 +918,12 @@ Similarly, if the client enforces DNSSEC validation on A/AAAA responses,
it SHOULD abandon the connection attempt if the HTTPSSVC response fails
to validate.

Finally, when making an "https" scheme request to an origin with an HTTPSSVC
record, either directly or via the above redirect, client SHOULD terminate the
connection if there are any errors with the underlying secure transport, such as
errors in certificate validation. This aligns with Section 8.4 and Section 12.1
of {{HSTS}}.

# Alt-Svc and SVCB/HTTPSSVC parameter for ESNI keys {#esniconfig}

Both SVCB/HTTPSSVC and Alt-Svc "esniconfig" parameters are defined for
Expand Down

0 comments on commit 26e93ec

Please sign in to comment.