Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update HTTP/1.1 ref #1350

Merged
merged 1 commit into from
May 27, 2024
Merged

Update HTTP/1.1 ref #1350

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions draft-ietf-tls-rfc8446bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,6 @@ informative:
RFC6091:
RFC6520:
RFC8305:
RFC7230:
RFC7250:
RFC7465:
RFC7568:
Expand All @@ -87,6 +86,7 @@ informative:
RFC8849:
RFC9345:
RFC8870:
RFC9112:
RFC9162:
RFC9146:
RFC8844:
Expand Down Expand Up @@ -5327,7 +5327,7 @@ Clients SHOULD NOT reuse a ticket for multiple connections. Reuse
of a ticket allows passive observers to correlate different connections.
Servers that issue tickets SHOULD offer at least as many tickets
as the number of connections that a client might use; for example, a web browser
using HTTP/1.1 {{RFC7230}} might open six connections to a server. Servers SHOULD
using HTTP/1.1 {{RFC9112}} might open six connections to a server. Servers SHOULD
issue new tickets with every connection. This ensures that clients are
always able to use a new ticket when creating a new connection.

Expand Down
Loading