delta/curl.git/tests/data/test1123, branch bagder/test493-https github.com: bagder/curl.git tests: use %TESTNUMBER instead of fixed number 2021-03-19T14:57:21+00:00 Daniel Stenberg daniel@haxx.se 2021-03-12T16:38:26+00:00 e2b4df7b5ed8ed86c900820fc4b2c30b9cb53f51 This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 
This makes the tests easier to copy and relocate to other test numbers
without having to update content.

Closes #6738
runtests: provide curl's version string as %VERSION for tests 2020-10-02T20:54:23+00:00 Daniel Stenberg daniel@haxx.se 2020-10-02T11:45:24+00:00 e6b21d422e631a7c0cc81abf956af179b3b4c5e8 ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037 
... so that we can check HTTP requests for User-Agent: curl/%VERSION

Update 600+ test cases accordingly.

Closes #6037
tests: unified use of some keywords 2014-04-03T09:49:49+00:00 Dan Fandrich dan@coneharvesters.com 2014-04-03T09:46:13+00:00 c57166b575c706fbbf697e1536c9ef363f35ef40 






transfer-encoding: added new option and cmdline
2011-04-18T17:46:21+00:00

Daniel Stenberg
daniel@haxx.se

2011-04-14T20:45:42+00:00

8e4fb01e64bee1893452f25873758cb856898d84

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.





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.







TE: do the Connection: header
2011-04-18T17:46:21+00:00

Daniel Stenberg
daniel@haxx.se

2011-04-11T14:30:14+00:00

9d191a6a40c2e90153d4b60cbc78fa34837c07ee

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:.





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:.







HTTP: add support for gzip and deflate Transfer-Encoding
2011-04-18T17:46:21+00:00

Daniel Stenberg
daniel@haxx.se

2011-04-05T21:24:52+00:00

0790b2791091ca46bed3813dc7d04cd3f30e5dac

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.





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.