Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.compression > #2342
| From | Phil Carmody <thefatphil_demunged@yahoo.co.uk> |
|---|---|
| Newsgroups | comp.compression |
| Subject | Re: Standardisation of header compression in HTTP 2 |
| Date | 2014-06-01 12:11 +0300 |
| Organization | A noiseless patient Spider |
| Message-ID | <871tv9j8pe.fsf@bazspaz.fatphil.org> (permalink) |
| References | <btdmlaFir9rU1@mid.individual.net> <lksejg$d2o$1@news2.informatik.uni-stuttgart.de> <k9h3n99cjge04cdqi4a10bj641q0ibflo6@4ax.com> <lkt09u$haj$1@news2.informatik.uni-stuttgart.de> <eli$1405131506@qz.little-neck.ny.us> |
Eli the Bearded <*@eli.users.panix.com> writes: > In comp.compression, Thomas Richter <thor@math.tu-berlin.de> wrote: > > Am 13.05.2014 09:26, schrieb Robert Wessel: > >> As to the purpose of HTTP header compression, many of the headers have > >> gotten fairly bulky, what with contents of cookies, the web site name, > >> modifications dates, encoding types, agent/server IDs, and whatnot, > >> plus you often see many headers when you have HTTP 1.1 persistent > >> connections, often for many smallish chunks of web page, especially > >> when you see dozens of GETs for unchanged pages in a single session, > >> where there are thousands of header bytes exchanged, with no data at > > Well... ok. That's all I can say, looks weird to me as I would have > > guessed otherwise, but if you say. > > There are a few very obvious large items in a typical web page, and > many, many more small and less obvious ones. Look at a web site > load analysis for examples. With Pingdom Website Speed Test: > > http://tools.pingdom.com/fpt/ > > And entering "www.latimes.com", it finds 146 individual requests making > up the page. Many of these have a content body size of zero bytes, and > probably half of them are 1kB or less. > > Compressed headers will make web bugs and other tracking tools much less > bandwidth intensive, and thus cheaper to do. Don't you want site > operators to be able to track you better? The obvious optimisation is to simply not send all that shit. HTTP 1.1 was clearly a prototype of a much larger system... http://www.youtube.com/watch?v=9L_73vDgBjU Phil -- Religion is too important a matter to its devotees to be a subject of ridicule. If they indulge in absurdities, they are to be pitied rather than ridiculed. -- Immanuel Kant (1724-1804), lecture at Konigsberg, 1775
Back to comp.compression | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Standardisation of header compression in HTTP 2 pgut001@cs.auckland.ac.nz (Peter Gutmann) - 2014-05-13 04:50 +0000
Re: Standardisation of header compression in HTTP 2 Thomas Richter <thor@math.tu-berlin.de> - 2014-05-13 08:37 +0200
Re: Standardisation of header compression in HTTP 2 Robert Wessel <robertwessel2@yahoo.com> - 2014-05-13 02:26 -0500
Re: Standardisation of header compression in HTTP 2 Thomas Richter <thor@math.tu-berlin.de> - 2014-05-13 13:39 +0200
Re: Standardisation of header compression in HTTP 2 Eli the Bearded <*@eli.users.panix.com> - 2014-05-13 19:19 +0000
Re: Standardisation of header compression in HTTP 2 Thomas Richter <thor@math.tu-berlin.de> - 2014-05-14 11:44 +0200
Re: Standardisation of header compression in HTTP 2 Robert Wessel <robertwessel2@yahoo.com> - 2014-05-14 12:08 -0500
Re: Standardisation of header compression in HTTP 2 Phil Carmody <thefatphil_demunged@yahoo.co.uk> - 2014-06-01 12:11 +0300
Re: Standardisation of header compression in HTTP 2 Eli the Bearded <*@eli.users.panix.com> - 2014-06-03 20:00 +0000
Re: Standardisation of header compression in HTTP 2 matrix29bear@gmail.com - 2014-06-11 00:53 -0700
Re: Standardisation of header compression in HTTP 2 glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2014-05-13 08:35 +0000
csiph-web