HTTP/HTML Integration Semantics
From Chapter 3, we recall that HTTP headers may give new meaning to the entire response (Location, Transfer-Encoding, and so on), change the way the payload is presented (Content-Type, Content-Disposition), or affect the client-side environment in other, auxiliary ways (Refresh, Set-Cookie, Cache-Control, Expires, etc.).
But what if an HTML document is delivered through a non-HTTP protocol or loaded from a local file? Clearly, in this case, there is no simple way to express or preserve this information. We can part with some of it easily, but parameters such as the MIME type or the character set are essential, and losing them forces browsers to improvise later on. (Consider, for example, that charsets such as UTF-7, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access