3 ms·
Response headers: HTTP/1.1 200 k Content-Length: 1163 content-encoding: deflate I guess the '200 k' instead of '200 OK' saves an extra byte! :) Howe
by joosters 9y ago
Response headers:
HTTP/1.1 200 k
Content-Length: 1163
content-encoding: deflate
I guess the '200 k' instead of '200 OK' saves an extra byte! :)
However, since they don't do any HTTP keep-alives (the connection sends a HTTP response and closes before you even send it anything), couldn't they save some space by dropping the Content-Length? It's an optional header.
- raggi 9y agoNot unless they switch to http/1.0. in 1.1 you need one of: content length, connection close, chunked encoding.
- joosters 9y agoTrue, their server should be returning HTTP/1.0. It's a shame that you can't get away with replacing the initial HTTP/1.0 with HTTP/1 and shave off another couple of bytes :) Edit: I wonder if you could go full retro and just return a HTTP/0.9 response (no HTTP headers at all, just the page contents). If they then put back the DEFLATE/GZIP header bits, perhaps a browser would spot that the contents are compressed and do the decompression...