Takeaways
- This status code indicates to the client that the server is likely to send a final response with the header fields included in the informational response.
- Typically, a server will include the header fields sent in a
103 Early Hints
response in the final response as well. However, there might be cases when this is not desirable, such as when the server learns that the header fields in the103 Early Hints
response are not correct before the final response is sent. - A client can speculatively evaluate the header fields included in a
103 Early Hints
response while waiting for the final response. For example, a client might recognize aLink
header field value containing the relation typepreload
and start fetching the target resource. However, these header fields only provide hints to the client; they do not replace the header fields on the final response. - Aside from performance optimizations, such evaluation of the
103 Early Hints
response's header fields must not affect how the final response is processed. A client must not interpret the103 Early Hints
response header fields as if they applied to the informational response itself (e.g., as metadata about the response). - A server may use a
103 Early Hints
response to indicate only some of the header fields that are expected to be found in the final response. A client should not interpret the non-existence of a header field in a103 Early Hints
response as a speculation that the header field is unlikely to be part of the final response.
Information
The HTTP 103 Early Hints
information response status code is primarily intended to be used with the Link
header to allow the user agent to start preloading resources while the server is still preparing a response.