aboutsummaryrefslogtreecommitdiff
path: root/tests/data
AgeCommit message (Collapse)Author
2016-06-19tests: fix the HTTP/2 testsDaniel Stenberg
The HTTP/2 tests brought with commit bf05606ef1f were using the internal name 'http2' for the HTTP/2 server, while in fact that name was already used for the second instance of the HTTP server. This made tests using the second instance (like test 2050) fail after a HTTP/2 test had run. The server is now known as HTTP/2 internally and within the <server> section in test cases. 1700, 1701 and 1702 were updated accordingly.
2016-06-15tests: Added HTTP proxy keywords to tests 1141 & 1142Dan Fandrich
2016-06-06tests: two more HTTP/2 testsDaniel Stenberg
1701 and 1702
2016-06-06runtests: make stripfile work on stdout as wellDaniel Stenberg
... and have test 1700 use that to strip out the nghttpx server: headers
2016-06-06http2-tests: test1700 is the first real HTTP/2 testDaniel Stenberg
It requires that 'nghttpx' is in the PATH, and it will run the tests using nghttpx as a front-end proxy in front of the standard HTTP/1 test server. This uses HTTP/2 over plain TCP. If you like me have nghttpx installed in a custom path, you can run test 1700 like this: $ PATH=$PATH:$HOME/build-nghttp2/bin/ ./runtests.pl 1700
2016-05-30URL parser: allow URLs to use one, two or three slashesDaniel Stenberg
Mostly in order to support broken web sites that redirect to broken URLs that are accepted by browsers. Browsers are typically even more leniant than this as the WHATWG URL spec they should allow an _infinite_ amount. I tested 8000 slashes with Firefox and it just worked. Added test case 1141, 1142 and 1143 to verify the new parser. Closes #791
2016-05-13mprintf: Fix processing of width and prec argsJay Satiro
Prior to this change a width arg could be erroneously output, and also width and precision args could not be used together without crashing. "%0*d%s", 2, 9, "foo" Before: "092" After: "09foo" "%*.*s", 5, 2, "foo" Before: crash After: " fo" Test 557 is updated to verify this and more
2016-05-01test1140: run nroff-scan to verify man pagesDaniel Stenberg
2016-04-29curl -J: make it work even without http:// scheme on URLJay Satiro
It does open up a miniscule risk that one of the other protocols that libcurl could use would send back a Content-Disposition header and then curl would act on it even if not HTTP. A future mitigation for this risk would be to allow the callback to ask libcurl which protocol is being used. Verified with test 1312 Closes #760
2016-04-28test1139: verifies libcurl option man page presenceDaniel Stenberg
- checks that each option has its own man page present - checks that each option is mentioned in its corresponding index man page
2016-04-25test1322: verify stripping of trailing dot from host nameDaniel Stenberg
While being debated (in #716) and a violation of RFC 7230 section 5.4, this test verifies that the existing functionality works as intended. It strips the dot from the host name and uses the host without dot throughout the internals.
2016-04-25test148: fixed after the --ftp-create-dirs retry changeDaniel Stenberg
follow-up commit to 3c1e84f569 as it made curl try a little harder
2016-04-20tests: added test1517Karlson2k
... for checking ability to receive full HTTP response when POST request is used with slow read callback function. This test checks for bug #657 and verifies the work-around from 72d5e144fbc6. Closes #720
2016-04-17news: CURLOPT_CONNECT_TO and --connect-toMichael Kaufmann
Makes curl connect to the given host+port instead of the host+port found in the URL.
2016-03-10cookies: first n/v pair in Set-Cookie: is the cookie, then parametersDaniel Stenberg
RFC 6265 section 4.1.1 spells out that the first name/value pair in the header is the actual cookie name and content, while the following are the parameters. libcurl previously had a more liberal approach which causes significant problems when introducing new cookie parameters, like the suggested new cookie priority draft. The previous logic read all n/v pairs from left-to-right and the first name used that wassn't a known parameter name would be used as the cookie name, thus accepting "Set-Cookie: Max-Age=2; person=daniel" to be a cookie named 'person' while an RFC 6265 compliant parser should consider that to be a cookie named 'Max-Age' with an (unknown) parameter 'person'. Fixes #709
2016-03-08cookie: do not refuse cookies for localhostTim Rühsen
Closes #658
2016-03-06test46: change cookie expiry dateDaniel Stenberg
Since two of the cookies would now otherwise expire and cause the test to fail after commit 20de9b4f09 Discussed in #697
2016-02-23TFTP: add option to suppress TFTP option requests (Part 2)Jay Satiro
- Add tests. - Add an example to CURLOPT_TFTP_NO_OPTIONS.3. - Add --tftp-no-options to expose CURLOPT_TFTP_NO_OPTIONS. Bug: https://github.com/curl/curl/issues/481
2016-02-20Enabled test 1437 after the bug fix in commit 3fa220a6Dan Fandrich
2016-02-19Added test 1437 to verify a memory leakDan Fandrich
Reported-by: neex@users.noreply.github.com
2016-02-13test1604: Add to Makefile.inc so it gets runDan Fandrich
2016-02-08cookies: allow spaces in cookie names, cut of trailing spacesDaniel Stenberg
It turns out Firefox and Chrome both allow spaces in cookie names and there are sites out there using that. Turned out the code meant to strip off trailing space from cookie names didn't work. Fixed now. Test case 8 modified to verify both these changes. Closes #639
2016-02-08Proxy-Connection: stop sending this header by defaultDaniel Stenberg
RFC 7230 says we should stop. Firefox already stopped. Bug: https://github.com/curl/curl/issues/633 Reported-By: Brad Fitzpatrick Closes #633
2016-02-05tool_doswin: Improve sanitization processingJay Satiro
- Add unit test 1604 to test the sanitize_file_name function. - Use -DCURL_STATICLIB when building libcurltool for unit testing. - Better detection of reserved DOS device names. - New flags to modify sanitize behavior: SANITIZE_ALLOW_COLONS: Allow colons SANITIZE_ALLOW_PATH: Allow path separators and colons SANITIZE_ALLOW_RESERVED: Allow reserved device names SANITIZE_ALLOW_TRUNCATE: Allow truncating a long filename - Restore sanitization of banned characters from user-specified outfile. Prior to this commit sanitization of a user-specified outfile was temporarily disabled in 2b6dadc because there was no way to allow path separators and colons through while replacing other banned characters. Now in such a case we call the sanitize function with SANITIZE_ALLOW_PATH which allows path separators and colons to pass through. Closes https://github.com/curl/curl/issues/624 Reported-by: Octavio Schroeder
2016-02-04URLs: follow GitHub project rename (also Travis CI)Viktor Szakats
Closes #632
2016-02-03URLs: change all http:// URLs to https://Daniel Stenberg
2016-01-18tests: Add a test for pinnedpubkey fail even when insecureJay Satiro
Because disabling the peer verification (--insecure) must not disable the public key pinning check (--pinnedpubkey).
2016-01-11lib: Prefix URLs with lower-case protocol names/schemesMohammad AlSaleh
Before this patch, if a URL does not start with the protocol name/scheme, effective URLs would be prefixed with upper-case protocol names/schemes. This behavior might not be expected by library users or end users. For example, if `CURLOPT_DEFAULT_PROTOCOL` is set to "https". And the URL is "hostname/path". The effective URL would be "HTTPS://hostname/path" instead of "https://hostname/path". After this patch, effective URLs would be prefixed with a lower-case protocol name/scheme. Closes #597 Signed-off-by: Mohammad AlSaleh <CE.Mohammad.AlSaleh@gmail.com>
2016-01-08connection reuse: IDN host names fixedMichael Kaufmann
Use the ACE form of IDN hostnames as key in the connection cache. Add new tests. Closes #592
2016-01-07tests: mark IPv6 FTP and FTPS tests with the FTP keywordDaniel Stenberg
2015-12-26test 1515: add data checkMarc Hoersken
2015-12-26test 1515: add MSYS support by passing a relative pathMarc Hoersken
MSYS would otherwise turn a /-style path into a C:\-style path.
2015-12-26test 539: use datacheck mode text for ASCII-mode LISTingsMarc Hoersken
While still using datacheck mode binary for the inline reply data.
2015-12-24tests 1048 and 1050: use datacheck mode text for ASCII-mode LISTingsMarc Hoersken
2015-12-24tests 706 and 707: use datacheck mode text for ASCII-mode LISTingsMarc Hoersken
2015-12-24tests 400,403,406: use datacheck mode text for ASCII-mode LISTingsMarc Hoersken
2015-12-23test 16: fix on Linux (and Windows) by using plain ASCII charactersMarc Hoersken
Follow up on b064ff0c351bb287557228575ef4c1d079b866fb, thanks Daniel.
2015-12-23tests 252-255: use datacheck mode text for ASCII-mode LISTingsMarc Hoersken
2015-12-23test 16: fix on Windows by converting data file from ANSI to UTF-8Marc Hoersken
2015-12-17test 1326: fix file check since curl is outputting binary dataMarc Hoersken
2015-12-17test 1326: fix getting stuck on Windows due to incomplete requestMarc Hoersken
The request needs to be read and send in binary mode in order to use CRLF instead of LF. Adding --upload-file - causes curl to read stdin in binary mode.
2015-12-13curl: use 2TLS by defaultDaniel Stenberg
Make this the default for the curl tool (if built with HTTP/2 powers enabled) unless a specific HTTP version is requested on the command line. This should allow more users to get HTTP/2 powers without having to change anything.
2015-12-03tests: Corrected copy and pasted comments from commit e643c5c908Steve Holme
2015-12-02test947: Corrected typo in test nameSteve Holme
2015-12-02tests: Disable the OAUTHBEARER tests when using a non-default port numberSteve Holme
Tests 842, 843, 844, 845, 887, 888, 889, 890, 946, 947, 948 and 949 fail if a custom port number is specified via the -b option of runtests.pl. Suggested by: Kamil Dudka Bug: http://curl.haxx.se/mail/lib-2015-12/0003.html
2015-11-24test1513: make sure the callback is only called onceDaniel Stenberg
2015-11-21Makefile.inc: Fixed test run errorSteve Holme
test845 not present in tests/data/Makefile.inc
2015-11-20tests: Re-enabled tests 889 and 890 following POP3 fixSteve Holme
2015-11-15tests: Disabled 889 and 890 until we support POP3 continuation responsesSteve Holme
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.
2015-11-15tests: Corrected typos from commit ba4d8f7ebaSteve Holme
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-05 17:15:30 +0000