moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-14 13:35:03 -05:00
Code Issues Releases Wiki Activity
57476a91e4
curl/tests/data/test1142

68 lines
1.0 KiB
Plaintext
Raw Normal View History

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 09:11:10 -04:00
<testcase>
<info>
<keywords>
HTTP
HTTP GET
tests: Added HTTP proxy keywords to tests 1141 & 1142
2016-06-15 17:04:48 -04:00
HTTP proxy
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 09:11:10 -04:00
followlocation
</keywords>
</info>
# Server-side
<reply>
<data>
HTTP/1.1 302 This is a weirdo text message
Connection: close
Location: http:////foo.example.com/want/11420001
This server reply is for testing
</data>
<data1>
HTTP/1.1 200 hello
Connection: close
Content-Length: 4
hej
</data1>
<datacheck>
HTTP/1.1 302 This is a weirdo text message
Connection: close
Location: http:////foo.example.com/want/11420001
</datacheck>
</reply>
# Client-side
<client>
<server>
http
</server>
<name>
HTTP redirect to http://// (four slashes!)
</name>
<command>
%HOSTIP:%HTTPPORT/want/1142 -L -x http://%HOSTIP:%HTTPPORT
</command>
tests: use proxy feature This makes the tests succeed when using --disable-proxy. Closes https://github.com/curl/curl/pull/4488
2019-10-14 16:29:19 -04:00
<features>
proxy
</features>
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 09:11:10 -04:00
</client>
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET http://%HOSTIP:%HTTPPORT/want/1142 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*
proxy: fix tests as follow-up to 93b0d907d5 This fixes tests that were added after 113f04e664b as the tests would fail otherwise. We bring back "Proxy-Connection: Keep-Alive" now unconditionally to fix regressions with old and stupid proxies, but we could possibly switch to using it only for CONNECT or only for NTLM in a future if we want to gradually reduce it. Fixes #954 Reported-by: János Fekete
2016-08-16 04:14:48 -04:00
Proxy-Connection: Keep-Alive
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 09:11:10 -04:00
</protocol>
# 3, CURLE_URL_MALFORMAT for the four slashes
<errorcode>
3
</errorcode>
</verify>
</testcase>
Reference in New Issue Copy Permalink