Skip to content
  1. Apr 27, 2011
  2. Apr 26, 2011
  3. Apr 25, 2011
  4. Apr 24, 2011
  5. Apr 22, 2011
  6. Apr 21, 2011
  7. Apr 20, 2011
  8. Apr 19, 2011
  9. Apr 18, 2011
    • Daniel Stenberg's avatar
      transfer-encoding: document the options · 5aae3c13
      Daniel Stenberg authored
      The new libcurl and command line options are now described.
      5aae3c13
    • Daniel Stenberg's avatar
      transfer-encoding: added new option and cmdline · 8e4fb01e
      Daniel Stenberg authored
      Added CURLOPT_TRANSFER_ENCODING as the option to set to request Transfer
      Encoding in HTTP requests (if built zlib enabled). I also renamed
      CURLOPT_ENCODING to CURLOPT_ACCEPT_ENCODING (while keeping the old name
      around) to reduce the confusion when we have to encoding options for
      HTTP.
      
      --tr-encoding is now the new command line option for curl to request
      this, and thus I updated the test cases accordingly.
      8e4fb01e
    • Daniel Stenberg's avatar
    • Daniel Stenberg's avatar
      TE: do the Connection: header · 9d191a6a
      Daniel Stenberg authored
      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:.
      9d191a6a
    • Daniel Stenberg's avatar
      TE: rename struct field content_encoding · 2db6f7e7
      Daniel Stenberg authored
      Since this struct member is used in the code to determine what and how
      to decode automatically and since it is now also used for compressed
      Transfer-Encodings, I renamed it to the more suitable 'auto_decoding'
      2db6f7e7
    • Daniel Stenberg's avatar
      HTTP: add support for gzip and deflate Transfer-Encoding · 0790b279
      Daniel Stenberg authored
      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.
      0790b279
  10. Apr 17, 2011
  11. Apr 15, 2011
  12. Apr 14, 2011