curl/tests/data/test1653

<testcase>
<info>
<keywords>
unittest
urlapi
</keywords>
</info>

<client>
<server>
none
</server>
<features>
unittest
</features>
<name>
urlapi port number parsing
</name>
</client>
</testcase>
tests: add urlapi unittest This adds a new unittest intended to cover the internal functions in the urlapi code, starting with parse_port(). In order to avoid name collisions in debug builds, parse_port() is renamed Curl_parse_port() since it will be exported. Reviewed-by: Daniel Stenberg <daniel@haxx.se> Reviewed-by: Marcel Raad <Marcel.Raad@teamviewer.com> 2018-12-11 15:02:24 +01:00			`<testcase>`
			`<info>`
			`<keywords>`
			`unittest`
			`urlapi`
			`</keywords>`
			`</info>`

			`<client>`
			`<server>`
			`none`
			`</server>`
			`<features>`
			`unittest`
			`</features>`
			`<name>`
urlapi: don't accept blank port number field without scheme ... as it makes the URL parser accept "very-long-hostname://" as a valid host name and we don't want that. The parser now only accepts a blank (no digits) after the colon if the URL starts with a scheme. Reported-by: d4d on hackerone Closes #6283 2020-12-04 17:27:57 +01:00			`urlapi port number parsing`
tests: add urlapi unittest This adds a new unittest intended to cover the internal functions in the urlapi code, starting with parse_port(). In order to avoid name collisions in debug builds, parse_port() is renamed Curl_parse_port() since it will be exported. Reviewed-by: Daniel Stenberg <daniel@haxx.se> Reviewed-by: Marcel Raad <Marcel.Raad@teamviewer.com> 2018-12-11 15:02:24 +01:00			`</name>`
			`</client>`
			`</testcase>`