2 Commits

Author	SHA1	Message	Date
Daniel Stenberg	9d191a6a40	TE: do the Connection: header ... When TE: is inserted in the request, we must add a "Connection: TE" as well to be HTTP 1.1 compliant. If a custom Connection: header is passed in, we must use that and only append TE to it. Test case 1125 verifies TE: + custom Connection:.	2011-04-18 19:46:21 +02:00
Daniel Stenberg	0790b27910	HTTP: add support for gzip and deflate Transfer-Encoding ... Transfer-Encoding differs from Content-Encoding in a few subtle ways, but primarily it concerns the transfer only and not the content so when discovered to be compressed we know we have to uncompress it. There will only arrive compressed transfers in a response after we have requested them with the appropriate TE: header. Test case 1122 and 1123 verify.	2011-04-18 19:46:21 +02:00