| #
a62ece3f |
| 05-Jul-2021 |
Daniel Stenberg |
c-hyper: bail on too long response headers
To match with built-in behaviors. Makes test 1154 work.
Closes #7350
|
| #
e41feede |
| 05-Jul-2021 |
Daniel Stenberg |
test1116: hyper doesn't pass through "surprise-trailers"
Closes #7344
|
| #
07fa74d3 |
| 01-Jul-2021 |
Daniel Stenberg |
test1519: adjusted to work with hyper
Closes #7333
|
| #
a80f8ea1 |
| 01-Jul-2021 |
Daniel Stenberg |
test1518: adjusted to work with hyper
... by making sure the stdout output doesn't look like HTTP headers.
Closes #7333
|
| #
7f11282d |
| 01-Jul-2021 |
Daniel Stenberg |
test1514: add a CRLF to the response to make it correct
Makes hyper accept it fine instead returning HYPERE_UNEXPECTED_EOF on
us.
Closes #7334
|
| #
80e1054f |
| 16-Jun-2021 |
Daniel Stenberg |
hyper: propagate errors back up from read callbacks
Makes test 513 work with hyper
Closes #7266
|
| #
7cfd8f03 |
| 08-Jun-2021 |
Daniel Stenberg |
tests/data/DISABLED: add tests not working with hyper
The goal is to remove them all from here over time.
Closes #7209
|
|
Revision tags: curl-7_76_1, curl-7_76_0, curl-7_75_0, curl-7_74_0, curl-7_73_0, tiny-curl-7_72_0, curl-7_72_0, curl-7_71_1, curl-7_71_0, curl-7_70_0, curl-7_69_1, curl-7_69_0, curl-7_68_0, curl-7_67_0, curl-7_66_0, curl-7_65_3, curl-7_65_2, curl-7_65_1, curl-7_65_0, curl-7_64_1, curl-7_64_0, curl-7_63_0, curl-7_62_0, curl-7_61_1, curl-7_61_0, curl-7_60_0, curl-7_59_0, curl-7_58_0, curl-7_57_0, curl-7_56_1, curl-7_56_0, curl-7_55_1, curl-7_55_0, curl-7_54_1, curl-7_54_0, curl-7_53_1, curl-7_53_0, curl-7_52_1, curl-7_52_0, curl-7_51_0, curl-7_50_3, curl-7_50_2, curl-7_50_1, curl-7_50_0, curl-7_49_1, curl-7_49_0, curl-7_48_0, curl-7_47_1, curl-7_47_0, curl-7_46_0, curl-7_45_0, curl-7_44_0, curl-7_43_0, curl-7_42_1, curl-7_42_0, curl-7_41_0, curl-7_40_0, curl-7_39_0, curl-7_38_0, curl-7_37_1, curl-7_37_0, curl-7_36_0, curl-7_35_0, curl-7_34_0, curl-7_33_0, curl-7_32_0, curl-7_31_0, curl-7_30_0, curl-7_29_0, curl-7_28_1 |
|
| #
3f0bef2b |
| 17-Nov-2012 |
Fabian Keil |
runtests.pl: add an -E option to specify an exclude file
It can contain additional restraints for test numbers,
keywords and tools.
The idea is to let third parties like the Pri
runtests.pl: add an -E option to specify an exclude file
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.
show more ...
|
| #
e50a877d |
| 05-Sep-2020 |
Daniel Stenberg |
tests: remove pipelining tests
Remove the tests 530, 584, 1900, 1901, 1902, 1903 and 2033. They were
previously disabled.
The Pipelining code was removed from curl in commit 2f4
tests: remove pipelining tests
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
show more ...
|
| #
75e8feb6 |
| 24-Apr-2020 |
Daniel Stenberg |
tests: make runtests check that disabled tests exists
... and error out if so. Removed '536' from DISABLED as there is no such
test file.
Closes #5288
|
| #
8a2b36df |
| 16-Mar-2020 |
Daniel Stenberg |
DISABLED: disable test 323
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.
DISABLED: disable test 323
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
show more ...
|
| #
b801b453 |
| 23-Sep-2018 |
Viktor Szakats |
whitespace fixes
- 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 inde
whitespace fixes
- 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
show more ...
|
| #
f7208df7 |
| 05-Sep-2018 |
Daniel Stenberg |
pipelining: deprecated
Transparently. The related curl_multi_setopt() options all still returns
OK when pipelining is selected.
To re-enable the support, the single line change
pipelining: deprecated
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
show more ...
|
| #
b7bdf210 |
| 01-Aug-2018 |
Daniel Stenberg |
test1307: disabled
Turns out that since we're using the native fnmatch function now when
available, and they simply disagree on a huge number of test patterns
that make it hard to te
test1307: disabled
Turns out that since we're using the native fnmatch function now when
available, and they simply disagree on a huge number of test patterns
that make it hard to test this function like this...
Fixes #2825
show more ...
|
| #
ac9a179f |
| 14-Jun-2018 |
Daniel Stenberg |
multi: fix memory leak when stopped during name resolve
When the application just started the transfer and then stops it while
the name resolve in the background thread hasn't completed,
multi: fix memory leak when stopped during name resolve
When the application just started the transfer and then stops it while
the name resolve in the background thread hasn't completed, we need to
wait for the resolve to complete and then cleanup data accordingly.
Enabled test 1553 again and added test 1590 to also check when the host
name resolves successfully.
Detected by OSS-fuzz.
Closes #1968
show more ...
|
| #
b2df2d47 |
| 07-Oct-2017 |
Daniel Stenberg |
Revert "multi_done: wait for name resolve to finish if still ongoing"
This reverts commit f3e03f6c0ac52a1bf396e03f7d7e9b5b3b7165fe.
Caused memory leaks in the fuzzer, needs to be do
Revert "multi_done: wait for name resolve to finish if still ongoing"
This reverts commit f3e03f6c0ac52a1bf396e03f7d7e9b5b3b7165fe.
Caused memory leaks in the fuzzer, needs to be done differently.
Disable test 1553 for now too, as it causes memory leaks without this
commit!
show more ...
|
| #
1ab9e9b5 |
| 03-Sep-2017 |
Patrick Monnerat |
lib: bump version info (soname). Adapt and reenable test 1135.
|
| #
3baf36ed |
| 02-Sep-2017 |
Patrick Monnerat |
mime: tests and examples.
Additional mime-specific tests.
Existing tests updated to reflect small differences (Expect: 100-continue,
data size change due to empty lines, etc).
Op
mime: tests and examples.
Additional mime-specific tests.
Existing tests updated to reflect small differences (Expect: 100-continue,
data size change due to empty lines, etc).
Option -F headers= keyword added to tests.
test1135 disabled until the entry point order change is resolved.
New example smtp-mime.
Examples postit2 and multi-post converted from form API to mime API.
show more ...
|
| #
f7df67cf |
| 26-Mar-2017 |
klemens |
spelling fixes
Closes #1356
|
| #
26e9fc27 |
| 09-Mar-2017 |
Daniel Stenberg |
tests: disabled 1903 now
Test 1903 is doing HTTP pipelining, and that is a timing and ordering
sensitive operation and this fails far too often on the Travis CI
leading to people mor
tests: disabled 1903 now
Test 1903 is doing HTTP pipelining, and that is a timing and ordering
sensitive operation and this fails far too often on the Travis CI
leading to people more or less ignoring test failures there. Not good.
The end of pipelning is probably coming sooner rather than later
anyway...
show more ...
|
| #
e50674ad |
| 20-Feb-2016 |
Dan Fandrich |
Enabled test 1437 after the bug fix in commit 3fa220a6
|
| #
fe37695a |
| 19-Feb-2016 |
Dan Fandrich |
Added test 1437 to verify a memory leak
Reported-by: neex@users.noreply.github.com
|
| #
20dcd195 |
| 03-Feb-2016 |
Viktor Szakats |
URLs: follow GitHub project rename (also Travis CI)
Closes #632
|
| #
bbb34b6f |
| 20-Nov-2015 |
Steve Holme |
tests: Re-enabled tests 889 and 890 following POP3 fix
|
| #
3c4065f4 |
| 15-Nov-2015 |
Steve Holme |
tests: Disabled 889 and 890 until we support POP3 continuation responses
As POP3 final and continuation responses both begin with a + character,
and both the finalcode and contcode varia
tests: Disabled 889 and 890 until we support POP3 continuation responses
As POP3 final and continuation responses both begin with a + character,
and both the finalcode and contcode variables in SASLprotoc are set as
such, we cannot tell the difference between them when we are expecting
an optional continuation from the server such as the following:
+ something else from the server
+OK final response
Disabled these tests until such a time we can tell the responses apart.
show more ...
|
