curl/tests/data/test1143

<testcase>
<info>
<keywords>
HTTP
HTTP GET
followlocation
</keywords>
</info>
# Server-side
<reply>
<data>
HTTP/1.1 200 hello
Connection: close
Content-Length: 4

hej
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP URL with http:/ (one slash!)
 </name>
 <command>
http:/%HOSTIP:%HTTPPORT/want/1143
</command>
<setenv>
# Needed for MSYS2 to not treat the argument as a POSIX path list
# that has to be converted to Windows paths
MSYS2_ARG_CONV_EXCL=http:/
</setenv>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /want/1143 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*

</protocol>
</verify>
</testcase>
URL parser: allow URLs to use one, two or three slashes 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-08 21:11:10 +08:00			`<testcase>`
			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`followlocation`
			`</keywords>`
			`</info>`
			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 200 hello`
			`Connection: close`
			`Content-Length: 4`

			`hej`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP URL with http:/ (one slash!)`
			`</name>`
			`<command>`
			`http:/%HOSTIP:%HTTPPORT/want/1143`
			`</command>`
test1143: disable MSYS2's POSIX path conversion By default, the MSYS2 bash interprets http:/%HOSTIP:%HTTPPORT/want/1143 as a POSIX file list and converts it to a Windows file list. Disable this with MSYS2_ARG_CONV_EXCL for the test to pass. Ref https://github.com/msys2/msys2/wiki/Porting#filesystem-namespaces Closes https://github.com/curl/curl/pull/2765 2018-07-20 17:00:57 +08:00			`<setenv>`
			`# Needed for MSYS2 to not treat the argument as a POSIX path list`
			`# that has to be converted to Windows paths`
			`MSYS2_ARG_CONV_EXCL=http:/`
			`</setenv>`
URL parser: allow URLs to use one, two or three slashes 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-08 21:11:10 +08:00			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`GET /want/1143 HTTP/1.1`
			`Host: %HOSTIP:%HTTPPORT`
			`Accept: /`

			`</protocol>`
			`</verify>`
			`</testcase>`