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

better clarify the differences between H2 server push #375

Merged
merged 3 commits into from Aug 7, 2017
Merged

better clarify the differences between H2 server push #375

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e086bf6
clarify the differences between H2 server push
kazuho Aug 4, 2017
2a1688d
"might consume less bandwidth" to avoid confusion
kazuho Aug 4, 2017
8168216
grammar fix
kazuho Aug 4, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-ietf-httpbis-early-hints.md
View file
Open in desktop
Expand Up @@ -68,7 +68,7 @@ final HTTP response are determined.

HTTP/2 ([RFC7540]) server push can accelerate the delivery of resources, but only resources for which the server is authoritative.
The other limitation of server push is that the response will be transmitted regardless of if the client has the response cached.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/if/whether/

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@martinthomson Thank you! Applied the change in 8168216.

At the cost of spending one extra round-trip compared to server push in the worst case, delivering Link header fields in a timely fashion is more flexible and consumes less bandwidth, especially if a client is associated with a large amount of cache storage.
At the cost of spending one extra round-trip compared to server push in the worst case, delivering Link header fields in a timely fashion is more flexible and might consume less bandwidth.

This memo defines a status code for sending an informational response ([RFC7231], Section 6.2) that
contains header fields that are likely to be included in the final response. A server can send the
Expand Down