misc: fix spelling mistakes

Reported-by: musvaage on github
Fixes #11171
Closes #11172
This commit is contained in:
Daniel Stenberg 2023-05-21 23:27:43 +02:00
parent 1561d06752
commit 127eb0d83a
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
28 changed files with 41 additions and 42 deletions

View file

@ -53,7 +53,7 @@ Accept: */*
</protocol>
# Hyper curl returns unsupported protocol
# bullt-in curl returns weird_server_reply
# built-in curl returns weird_server_reply
<errorcode>
%if hyper
1

View file

@ -30,7 +30,7 @@ CURLOPT_CURLU and CURLOPT_PORT
lib%TESTNUMBER
</tool>
# The tool does two requesets, the first sets CURLOPT_PORT to 1
# The tool does two requests, the first sets CURLOPT_PORT to 1
# the second resets the port again and expects that request to work.
<command>
http://%HOSTIP:%HTTPPORT/%TESTNUMBER

View file

@ -11,7 +11,7 @@ cookiejar
#
# The cookies set come in two versions. This is because when curl is built
# with Hyper, the API provides the headers already "sanitized" so we cannot
# compapare with the exact server contents unlesss it too sends the data
# compare with the exact server contents unless it too sends the data
# "clean".
<reply>

View file

@ -53,7 +53,7 @@ Accept: */*
</protocol>
# Hyper curl returns unsupported protocol
# bullt-in curl returns weird_server_reply
# built-in curl returns weird_server_reply
<errorcode>
%if hyper
1

View file

@ -34,7 +34,7 @@ Set-Cookie: mycookie1=; Path=/; Max-Age=-1; Expires=Thu, 01 Jan 1970 00:00:00 GM
http
</server>
<name>
Setting cookies set with expried dates that were loaded from jar
Setting cookies set with expired dates that were loaded from jar
</name>
<command>
http://%HOSTIP:%HTTPPORT/func_test/del_cookie -b %LOGDIR/cookie%TESTNUMBER -c %LOGDIR/save%TESTNUMBER

View file

@ -24,7 +24,7 @@
###########################################################################
# This script is intended for developers to test some internals of the
# runtests.pl harneess. Don't try to use this unless you know what you're
# runtests.pl harness. Don't try to use this unless you know what you're
# doing!
# An example command-line that starts a test http server for test 11 and waits

View file

@ -22,7 +22,7 @@
#
###########################################################################
# This module contains miscellanous functions needed in several parts of
# This module contains miscellaneous functions needed in several parts of
# the test suite.
package testutil;

View file

@ -76,7 +76,7 @@ static void expect_timer_seconds(struct Curl_easy *data, int seconds)
}
/* Scenario: simulate a redirect. When a redirect occurs, t_nslookup,
* t_connect, t_appconnect, t_pretransfer, and t_starttransfer are addative.
* t_connect, t_appconnect, t_pretransfer, and t_starttransfer are additive.
* E.g., if t_starttransfer took 2 seconds initially and took another 1
* second for the redirect request, then the resulting t_starttransfer should
* be 3 seconds. */

View file

@ -364,36 +364,36 @@ static struct test_case TEST_CASES[] = {
/* TIMEOUT_MS, FAIL_MS CREATED DURATION Result, HE_PREF */
/* CNCT HE v4 v6 v4 v6 MIN MAX */
{ 1, TURL, "test.com:123:192.0.2.1", CURL_IPRESOLVE_WHATEVER,
250, 150, 200, 200, 1, 0, 200, 500, R_FAIL, NULL },
250, 150, 200, 200, 1, 0, 200, 500, R_FAIL, NULL },
/* 1 ipv4, fails after ~200ms, reports COULDNT_CONNECT */
{ 2, TURL, "test.com:123:192.0.2.1,192.0.2.2", CURL_IPRESOLVE_WHATEVER,
500, 150, 200, 200, 2, 0, 400, 800, R_FAIL, NULL },
500, 150, 200, 200, 2, 0, 400, 800, R_FAIL, NULL },
/* 2 ipv4, fails after ~400ms, reports COULDNT_CONNECT */
#ifdef ENABLE_IPV6
{ 3, TURL, "test.com:123:::1", CURL_IPRESOLVE_WHATEVER,
250, 150, 200, 200, 0, 1, 200, 500, R_FAIL, NULL },
250, 150, 200, 200, 0, 1, 200, 500, R_FAIL, NULL },
/* 1 ipv6, fails after ~200ms, reports COULDNT_CONNECT */
{ 4, TURL, "test.com:123:::1,::2", CURL_IPRESOLVE_WHATEVER,
500, 150, 200, 200, 0, 2, 400, 800, R_FAIL, NULL },
500, 150, 200, 200, 0, 2, 400, 800, R_FAIL, NULL },
/* 2 ipv6, fails after ~400ms, reports COULDNT_CONNECT */
{ 5, TURL, "test.com:123:192.0.2.1,::1", CURL_IPRESOLVE_WHATEVER,
500, 150, 200, 200, 1, 1, 350, 800, R_FAIL, "v4" },
500, 150, 200, 200, 1, 1, 350, 800, R_FAIL, "v4" },
/* mixed ip4+6, v4 starts, v6 kicks in on HE, fails after ~350ms */
{ 6, TURL, "test.com:123:::1,192.0.2.1", CURL_IPRESOLVE_WHATEVER,
500, 150, 200, 200, 1, 1, 350, 800, R_FAIL, "v6" },
500, 150, 200, 200, 1, 1, 350, 800, R_FAIL, "v6" },
/* mixed ip6+4, v6 starts, v4 kicks in on HE, fails after ~350ms */
{ 7, TURL, "test.com:123:::1,192.0.2.1,::2,::3", CURL_IPRESOLVE_WHATEVER,
500, 600, 200, 200, 0, 3, 350, 800, R_FAIL, "v6" },
500, 600, 200, 200, 0, 3, 350, 800, R_FAIL, "v6" },
/* mixed ip6+4, v6 starts, v4 never starts due to high HE, TIMEOUT */
{ 8, TURL, "test.com:123:192.0.2.1,::1", CURL_IPRESOLVE_V4,
400, 150, 500, 500, 1, 0, 400, 600, R_FAIL, NULL },
400, 150, 500, 500, 1, 0, 400, 600, R_FAIL, NULL },
/* mixed ip4+6, but only use v4, check it uses full connect timeout,
although another address of the 'wrong' family is availbale */
although another address of the 'wrong' family is available */
{ 9, TURL, "test.com:123:::1,192.0.2.1", CURL_IPRESOLVE_V6,
400, 150, 500, 500, 0, 1, 400, 600, R_FAIL, NULL },
400, 150, 500, 500, 0, 1, 400, 600, R_FAIL, NULL },
/* mixed ip4+6, but only use v6, check it uses full connect timeout,
although another address of the 'wrong' family is availbale */
although another address of the 'wrong' family is available */
#endif
};