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.

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

adjust the explanation why it is difficult to generate the header block of a final response immediately #353

Merged
merged 1 commit into from May 30, 2017
Merged
Changes from all commits
Commits
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
8 changes: 4 additions & 4 deletions draft-ietf-httpbis-early-hints.md
Expand Up @@ -57,10 +57,10 @@ prior to their use; for example, rendering HTML by a Web browser. Having such li
the client as early as possible helps to minimize perceived latency.

The "preload" ([Preload]) link relation can be used to convey such links in the Link header field
of an HTTP response. However, it is not always possible for an origin server to generate a response
header block immediately after receiving a request. For example, the origin server might need to
query a database before generating a response, or it might delegate a request to an upstream HTTP
server running at a distant location.
of an HTTP response. However, it is not always possible for an origin server to generate the
header block of a final response immediately after receiving a request. For example, the origin
server might delegate a request to an upstream HTTP server running at a distant location, or the
status code might depend on the result of a database query.

The dilemma here is that even though it is preferable for an origin server to send some header fields as
soon as it receives a request, it cannot do so until the status code and the full header fields of the
Expand Down