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

add example #354

Merged
merged 1 commit into from May 30, 2017
Merged

add example #354

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
27 changes: 27 additions & 0 deletions draft-ietf-httpbis-early-hints.md
View file
Open in desktop
Expand Up @@ -105,6 +105,33 @@ response, or vice versa.
An intermediary MAY drop the informational response. It MAY send HTTP/2 ([RFC7540]) server pushes
using the information found in the 103 (Early Hints) response.

The following example illustrates a typical message exchange that involves a 103 (Early Hints) response.

Client request:

~~~ example
GET / HTTP/1.1
Host: example.com
~~~

Server response:

~~~ example
HTTP/1.1 103 Early Hints
Link: </style.css>; rel=preload; as=style
Link: </script.js>; rel=preload; as=script

HTTP/1.1 200 OK
Date: Fri, 26 May 2017 10:02:11 GMT
Content-Length: 1234
Content-Type: text/html; charset=utf-8
Link: </style.css>; rel=preload; as=style
Link: </script.js>; rel=preload; as=script

<!doctype html>
[... rest of the response body is ommitted from the example ...]
~~~

# Security Considerations

Some clients might have issues handling 103 (Early Hints), since informational responses are rarely
Expand Down