Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-04-30 | tests: Stop referring to server ports when they're not used | Dan Fandrich | |
Several tests referred to specific server ports even when the test didn't actually use that server or specify that it's needed. In such cases, the test harness substitutes the text "[not running]" as the port number which causes many such tests to fail due to the inability to parse the URL. These tests are changed to use %NOLISTENPORT which will always be substituted correctly. | |||
2017-03-08 | test1260: added http as a required feature | Dan Fandrich | |
2017-03-06 | test1260: removed errant XML tag | Dan Fandrich | |
2017-03-06 | URL: return error on malformed URLs with junk after port number | Daniel Stenberg | |
... because it causes confusion with users. Example URLs: "http://[127.0.0.1]:11211:80" which a lot of languages' URL parsers will parse and claim uses port number 80, while libcurl would use port number 11211. "http://user@example.com:80@localhost" which by the WHATWG URL spec will be treated to contain user name 'user@example.com' but according to RFC3986 is user name 'user' for the host 'example.com' and then port 80 is followed by "@localhost" Both these formats are now rejected, and verified so in test 1260. Reported-by: Orange Tsai |