Binary is probably a confusing term – everything is ultimately binary at some point in computers! HTTP/2 has a highly structured format where HTTP messages are formatted into packets (called frames) and where each frame is assigned to a stream. HTTP/2 frames have a specific format, including a length which is declared at the beginning … Read more
No common browsers support HTTP/1.1 trailers. Look at the column “Headers in trailer” in the “Network” tab of browserscope. Chrome: No, and won’t fix (bug). Supports H/2 trailers (bug). Firefox: No, and I don’t see a ticket in bugzilla for it. Appears to support H/2. IE: No Edge: No Safari: No Opera: Old versions only … Read more
The spec calls them “exchanges” (or “request/response exchanges”). Per section 1.4, “Overall Operation”: In HTTP/1.0, most implementations used a new connection for each request/response exchange. In HTTP/1.1, a connection may be used for one or more request/response exchanges […]
The spec calls them “exchanges” (or “request/response exchanges”). Per section 1.4, “Overall Operation”: In HTTP/1.0, most implementations used a new connection for each request/response exchange. In HTTP/1.1, a connection may be used for one or more request/response exchanges […]
The answer is: it depends. Suppose we have received If-None-Match: * If-Modified-Since: <yesterday date> And the page has been altered today. First, we take a look at the * which tells us: “Return 304 if the resource is there and condition (2) is met”. Fine, the resource exists, BUT condition (2) states: “Only return 304, … Read more
Proxy support and the Host field: HTTP 1.1 has a required Host header by spec. HTTP 1.0 does not officially require a Host header, but it doesn’t hurt to add one, and many applications (proxies) expect to see the Host header regardless of the protocol version. Example: GET / HTTP/1.1 Host: www.blahblahblahblah.com This header is … Read more