| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Closes #8128
|
|
|
|
| |
Closes #8128
|
|
|
|
|
|
| |
Minor reorg of the lib1156 code and it works fine for hyper.
Closes #8127
|
|
|
|
| |
Closes #8126
|
|
|
|
| |
Closes #8105
|
|
|
|
| |
Closes #8104
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is done by having native code do the haproxy header output before
hyper issues its request. The little downside with this approach is that
we need the entire Curl_buffer_send() function built, which is otherwise
not used for hyper builds.
If hyper ends up getting native support for the haproxy protocols we can
backpedal on this.
Enables test 1455 and 1456
Closes #8034
|
|
|
|
| |
Closes #7912
|
|
|
|
| |
Closes #7911
|
|
|
|
|
|
|
|
|
|
| |
... which then also includes negative ones as test 1430 uses.
This makes native + hyper backend act identically on this and therefore
test 1430 can now be enabled when building with hyper. Adjust test 1431
as well.
Closes #7909
|
|
|
|
| |
Closes #7905
|
|
|
|
|
|
| |
Verified by the enabled test 1288
Closes #7905
|
|
|
|
| |
Closes #7905
|
|
|
|
| |
Closes #7905
|
|
|
|
|
|
| |
Adjusted 1144, 1164 and 1176.
Closes #7900
|
|
|
|
|
|
|
|
| |
Simply because hyper doesn't have this ability. Mentioned in docs now.
Skip test 326 then
Closes #7889
|
|
|
|
|
|
|
| |
This test verifies that curl works with binary zeroes in HTTP response
headers and hyper refuses such. They're not kosher http.
Closes #7889
|
|
|
|
| |
Closes #7889
|
|
|
|
|
|
| |
Follow-up to 823d3ab855c
Closes #7889
|
|
|
|
|
|
|
| |
It returns HYPERE_UNEXPECTED_EOF for this case which we convert to the
somewhat generic CURLE_RECV_ERROR.
Closes #7889
|
|
|
|
|
|
| |
Enabled test 206
Closes #7888
|
|
|
|
|
|
|
|
| |
It uses revoked.badssl.com which now is expired and therefor this now
permafails. We should not use external sites for tests, this test should
be converted to use our own infra.
Closes #7845
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Triggered before a request is made but after a connection is set up
Changes:
- callback: Update docs and callback for pre-request callback
- Add documentation for CURLOPT_PREREQDATA and CURLOPT_PREREQFUNCTION,
- Add redirect test and callback failure test
- Note that the function may be called multiple times on a redirection
- Disable new 2086 test due to Windows weirdness
Closes #7477
|
|
|
|
|
|
|
|
|
| |
The test should be fine and it works for me repeated when run manually,
but clearly it causes CI failures and it needs more research.
Reported-by: RiderALT on github
Fixes #7725
Closes #7732
|
|
|
|
|
|
|
|
|
|
| |
By making them look less like http headers, the hyper mode "tweak"
doesn't interfere.
Enable test 2002 and 2003 in hyper builds (and 1280 which is unrelated
but should be enabled).
Closes #7658
|
|
|
|
|
| |
Fixes #7643
Closes #7649
|
|
|
|
|
|
|
|
|
|
| |
Make the built-in HTTP parser behave similar to hyper and reject any
HTTP response using more than 3 digits for the response code.
Updated test 1432 accordingly.
Enabled test 1432 in the hyper builds.
Closes #7641
|
|
|
|
| |
Closes #7638
|
|
|
|
|
|
| |
Enable test 1074
Closes #7617
|
|
|
|
|
|
| |
Enable test 1130 and 1131
Closes #7616
|
|
|
|
| |
Closes #7612
|
|
|
|
|
|
|
|
|
|
|
| |
Since this option is also used for FTP, it needs to work to set for
applications even if hyper doesn't support it for HTTP. Verified by test
1137.
Updated docs to specify that the option doesn't work for HTTP when using
the hyper backend.
Closes #7614
|
|
|
|
| |
Closes #7613
|
|
|
|
|
|
| |
Enable test 287
Closes #7598
|
|
|
|
|
|
|
|
| |
With the use hyper_request_on_informational()
Enable test 155 and 158
Closes #7597
|
|
|
|
|
|
| |
Enabled test 154
Closes #7568
|
|
|
|
|
|
| |
... so strip that from the test.
Closes #7349
|
|
|
|
|
|
| |
To match with built-in behaviors. Makes test 1154 work.
Closes #7350
|
|
|
|
| |
Closes #7344
|
|
|
|
| |
Closes #7333
|
|
|
|
|
|
| |
... by making sure the stdout output doesn't look like HTTP headers.
Closes #7333
|
|
|
|
|
|
|
| |
Makes hyper accept it fine instead returning HYPERE_UNEXPECTED_EOF on
us.
Closes #7334
|
|
|
|
|
|
| |
Makes test 513 work with hyper
Closes #7266
|
|
|
|
|
|
| |
The goal is to remove them all from here over time.
Closes #7209
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It can contain additional restraints for test numbers,
keywords and tools.
The idea is to let third parties like the Privoxy project
distribute an exclude file with their tarballs that specifies
which curl tests are not expected to work when using Privoxy
as a proxy, without having to fork the whole curl test suite.
The syntax could be changed to be extendable and maybe
more closely reflect the "curl test" syntax. Currently
it's a bunch of lines like these:
test:$TESTNUMBER:Reason why this test with number $TESTNUMBER should be skipped
keyword:$KEYWORD:Reason why tests whose keywords contain the $KEYWORD should be skipped
tool:$TOOL:Reason why tests with tools that contain $TOOL should be skipped
To specify multiple $TESTNUMBERs, $KEYWORDs and $TOOLs
on a single line, split them with commas.
|
|
|
|
|
|
|
|
|
|
| |
Remove the tests 530, 584, 1900, 1901, 1902, 1903 and 2033. They were
previously disabled.
The Pipelining code was removed from curl in commit 2f44e94efb3df8e,
April 2019.
Closes #5921
|
|
|
|
|
|
|
| |
... and error out if so. Removed '536' from DISABLED as there is no such
test file.
Closes #5288
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test uses SRP to "a server not supporting it" but modern stunnel
versions will silently accept it and remain happy. The test is therefore
faulty.
I haven't figured out how to make stunnel explicitly reject SRP-using
connects.
Reported-by: Marc Hörsken
Fixes #5105
Closes #5113
|
|
|
|
|
|
|
|
|
|
|
| |
- replace tabs with spaces where possible
- remove line ending spaces
- remove double/triple newlines at EOF
- fix a non-UTF-8 character
- cleanup a few indentations/line continuations
in manual examples
Closes https://github.com/curl/curl/pull/3037
|
|
|
|
|
|
|
|
|
|
|
|
| |
Transparently. The related curl_multi_setopt() options all still returns
OK when pipelining is selected.
To re-enable the support, the single line change in lib/multi.c needs to
be reverted.
See docs/DEPRECATE.md
Closes #2705
|