From 277c3303ddd9395cda751f7013299a5f5bdb03fa Mon Sep 17 00:00:00 2001 From: Kazuho Oku Date: Fri, 26 May 2017 10:14:36 +0900 Subject: [PATCH] add example --- draft-ietf-httpbis-early-hints.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/draft-ietf-httpbis-early-hints.md b/draft-ietf-httpbis-early-hints.md index cf716f937..6b0133eb4 100644 --- a/draft-ietf-httpbis-early-hints.md +++ b/draft-ietf-httpbis-early-hints.md @@ -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: ; rel=preload; as=style + Link: ; 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: ; rel=preload; as=style + Link: ; rel=preload; as=script + + + [... 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