- From: David Morris <dwm@xpasc.com>
- Date: Fri, 27 Jan 2012 13:46:18 -0800 (PST)
- cc: "'HTTP Working Group'" <ietf-http-wg@w3.org>
On Thu, 26 Jan 2012, Willy Tarreau wrote: > On Thu, Jan 26, 2012 at 08:39:00AM +0000, Poul-Henning Kamp wrote: > > In message <3242f7d9fe2f4046819ab4fcbafab251@treenet.co.nz>, Amos Jeffries writ > > es: > > > > >So how would compression type be embeded in the request-line in a way > > >not to break HTTP/1.1 servers receiving it? > > > > First of all, I would not allow different compression types. It's ZLIB > > and it's mandatory. > > I find it pretty cumbersome to force everyone to support zlib, especially > in environments where it provides no benefit (small requests/responses) > and only adds CPU usage and latency. It's especially true on intermediary > components which would have to decompress everything to be able to perform I talked with a hardware vendor yesterday who had implemented an HTTP server and client (and other stuff) in 128KB of ram in a special device. Adding mandatory zlib support would kill his product.
Received on Friday, 27 January 2012 21:46:54 UTC