SPDY increasing size of pages
Tom van der Woerdt
info at tvdw.eu
Wed Aug 8 10:45:57 UTC 2012
Op 8/8/12 12:40 PM, Valentin V. Bartenev schreef:
> On Wednesday 08 August 2012 14:14:07 Tom van der Woerdt wrote:
>> Quick tests show that my 805 byte file became a 813 byte response, which
>> seems consistent with the 8 byte header of a DATA frame.
>> Question: do we really need to include that into the size? Just like the
>> response headers aren't counted, why should the protocol overhead be
> This is how it is in nginx now. For example, if a response has been sent over
> HTTP with chunked transfer encoding, the $body_bytes_sent also will not equal
> to payload size.
> Personally I do not really agree with that, but it should be discussed and
> changed globally.
Ah, didn't know that.
>> Note: after refreshing the server responded with a 304 Not Modified but
>> it did log it as 813 bytes. Once I disabled SPDY, it logged a 0-byte
>> response. Both responses came without a content-length header so I am
>> assuming that the server didn't actually send a response body and this
>> too is a counting issue.
> Strange. How do you found out that it responded with 304 Not Modified?
That's what the logs say, and Firebug confirms it.
SPDY disabled: <ip> - tom [08/Aug/2012:12:42:38 +0200] "GET /home
HTTP/1.1" 304 0 "-" "<user agent>" "-"
SPDY enabled: <ip> - tom [08/Aug/2012:12:44:03 +0200] "GET /home
HTTP/1.1" 304 813 "-" "<user agent>" "-"
Both resulted in a 304 Not Modified.
More information about the nginx-devel