moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-12-25 01:28:51 -05:00
Code Issues Releases Wiki Activity
f21cc62832
curl/tests/data/test62

65 lines
1.2 KiB
Plaintext
Raw Normal View History

Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools.
2007-01-22 21:25:56 -05:00
<testcase>
keywords added
2005-04-22 17:59:08 -04:00
<info>
<keywords>
HTTP
HTTP GET
HTTP replaced headers
Added some <keywords> sections and use some key words more consistently.
2007-10-11 21:44:22 -04:00
cookies
made the cookie tests 61 and 62 test httponly cookies, both receiving in headers and reading from cookie-jar
2009-05-10 14:02:37 -04:00
httponly
keywords added
2005-04-22 17:59:08 -04:00
</keywords>
</info>
Added some <keywords> sections and use some key words more consistently.
2007-10-11 21:44:22 -04:00
send correct cookies when using a custom Host:
2003-05-02 05:12:26 -04:00
# Server-side
<reply>
<data>
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring.
2006-11-25 08:32:04 -05:00
HTTP/1.0 200 OK swsclose
send correct cookies when using a custom Host:
2003-05-02 05:12:26 -04:00
Date: Thu, 09 Nov 2010 14:49:00 GMT
Content-Type: text/html
boo
</data>
</reply>
# Client-side
<client>
<server>
http
</server>
<name>
HTTP, send cookies when using custom Host:
</name>
<command>
curl: create easy handles on-demand and not ahead of time This should again enable crazy-large download ranges of the style [1-10000000] that otherwise easily ran out of memory starting in 7.66.0 when this new handle allocating scheme was introduced. Reported-by: Peter Sumatra Fixes #4393 Closes #4438
2019-09-23 11:11:22 -04:00
http://%HOSTIP:%HTTPPORT/we/want/62 http://%HOSTIP:%HTTPPORT/we/want/62?hoge=fuga -b log/jar62.txt -H "Host: www.host.foo.com"
send correct cookies when using a custom Host:
2003-05-02 05:12:26 -04:00
</command>
<file name="log/jar62.txt">
# Netscape HTTP Cookie File
curl.se: new home Closes #6172
2020-11-04 08:02:01 -05:00
# https://curl.se/docs/http-cookies.html
send correct cookies when using a custom Host:
2003-05-02 05:12:26 -04:00
# This file was generated by libcurl! Edit at your own risk.
tests: allow tests to pass by 2037-02-12 similar to commit f508d29f3902104018 Closes #3443
2019-01-07 10:23:04 -05:00
#HttpOnly_.foo.com TRUE /we/want/ FALSE 2147483647 test yes
.host.foo.com TRUE /we/want/ FALSE 2147483647 test2 yes
.fake.host.foo.com TRUE /we/want/ FALSE 2147483647 test4 yes
send correct cookies when using a custom Host:
2003-05-02 05:12:26 -04:00
.foo.com TRUE /moo TRUE 0 test3 maybe
</file>
</client>
# Verify data after the test has been "shot"
<verify>
<protocol>
GET /we/want/62 HTTP/1.1
http: always send Host: header as first header ...after the method line: "Since the Host field-value is critical information for handling a request, a user agent SHOULD generate Host as the first header field following the request-line." / RFC 7230 section 5.4 Additionally, this will also make libcurl ignore multiple specified custom Host: headers and only use the first one. Test 1121 has been updated accordingly Bug: http://curl.haxx.se/bug/view.cgi?id=1491 Reported-by: Rainer Canavan
2015-03-11 19:50:46 -04:00
Host: www.host.foo.com
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037
2020-10-02 07:45:24 -04:00
User-Agent: curl/%VERSION
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 07:46:41 -05:00
Accept: */*
send correct cookies when using a custom Host:
2003-05-02 05:12:26 -04:00
Cookie: test2=yes; test=yes
curl: create easy handles on-demand and not ahead of time This should again enable crazy-large download ranges of the style [1-10000000] that otherwise easily ran out of memory starting in 7.66.0 when this new handle allocating scheme was introduced. Reported-by: Peter Sumatra Fixes #4393 Closes #4438
2019-09-23 11:11:22 -04:00
GET /we/want/62?hoge=fuga HTTP/1.1
http: always send Host: header as first header ...after the method line: "Since the Host field-value is critical information for handling a request, a user agent SHOULD generate Host as the first header field following the request-line." / RFC 7230 section 5.4 Additionally, this will also make libcurl ignore multiple specified custom Host: headers and only use the first one. Test 1121 has been updated accordingly Bug: http://curl.haxx.se/bug/view.cgi?id=1491 Reported-by: Rainer Canavan
2015-03-11 19:50:46 -04:00
Host: www.host.foo.com
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037
2020-10-02 07:45:24 -04:00
User-Agent: curl/%VERSION
cookies: follow-up fix for path checking The initial fix to only compare full path names were done in commit 04f52e9b4db0 but found out to be incomplete. This takes should make the change more complete and there's now two additional tests to verify (test 31 and 62).
2013-06-12 05:19:56 -04:00
Accept: */*
Cookie: test2=yes; test=yes
send correct cookies when using a custom Host:
2003-05-02 05:12:26 -04:00
</protocol>
</verify>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => &amp; ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools.
2007-01-22 21:25:56 -05:00
</testcase>
Reference in New Issue Copy Permalink