4 ms·
Just for curiosity's sake, it would be interesting to have an estimate on how many extra gigabytes have been sent over time with these headers.
by m0th87 16y ago
Just for curiosity's sake, it would be interesting to have an estimate on how many extra gigabytes have been sent over time with these headers.
- minouye 16y agoOr how many hires have come from this
- bkrausz 16y agoThe 2 header lines are 163 bytes (including /r/n). Quantcast (probably very wrong, but the best estimate I can find) says they get 277K visits per day. Not sure what their pages/visits are, but it's that times 43GB/day.
- someone_here 16y agoI think you mean 43MB/Day, not GB.
- bkrausz 16y agoDamn, you're right! Stupid orders of magnitude...
- deleted 16y ago[deleted]
- masklinn 16y agoYou didn't take gzipping in account. Taking it in account, it's 105 bytes.
- bkrausz 16y agoYou can't gzip headers, only content
- alnayyir 16y agoHeaders are how the clients know to gzip the content. You think http libs and web servers figure out whether or not something is gzipped by guessing? :)
- JoachimSchipper 16y agoAlthough it's not guilty of this particular idiocy, IE does like to override MIME types by content- or extension-based guesses. So it would, sadly, not be that surprising.