mirror/curl
2
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2024-11-27 05:50:21 +08:00
Code Issues Packages Projects Releases Wiki Activity
39a416f12a
curl/tests/data/test84

56 lines
923 B
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-23 10:25:56 +08:00
<testcase>
keyword update
2005-04-27 17:59:47 +08:00
<info>
<keywords>
HTTP
HTTP GET
HTTP Basic auth
HTTP proxy
</keywords>
</info>
more auth tests
2003-08-12 16:19:23 +08: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 21:32:04 +08:00
HTTP/1.0 200 OK
more auth tests
2003-08-12 16:19:23 +08:00
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake swsclose
Content-Type: text/html
Funny-head: yesyes
contents
</data>
</reply>
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP over proxy with site authentication
</name>
<command>
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script.
2004-09-08 16:08:38 +08:00
http://%HOSTIP:%HTTPPORT/we/want/that/page/84 -x %HOSTIP:%HTTPPORT --user iam:myself
more auth tests
2003-08-12 16:19:23 +08:00
</command>
A minor "syntax error" in numerous test files corrected
2005-01-26 05:45:03 +08:00
</client>
more auth tests
2003-08-12 16:19:23 +08:00
#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script.
2004-09-08 16:08:38 +08:00
GET http://127.0.0.1:%HTTPPORT/we/want/that/page/84 HTTP/1.1
more auth tests
2003-08-12 16:19:23 +08:00
Authorization: Basic aWFtOm15c2VsZg==
User-Agent: curl/7.10.7-pre2 (i686-pc-linux-gnu) libcurl/7.10.7-pre2 OpenSSL/0.9.7a zlib/1.1.3
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script.
2004-09-08 16:08:38 +08:00
Host: 127.0.0.1:%HTTPPORT
more auth tests
2003-08-12 16:19:23 +08:00
Pragma: no-cache
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 20:46:41 +08:00
Accept: */*
Modified the default HTTP headers used by libcurl: A) Normal non-proxy HTTP: - no more "Pragma: no-cache" (this only makes sense to proxies) B) Non-CONNECT HTTP request over proxy: - "Pragma: no-cache" is used (like before) - "Proxy-Connection: Keep-alive" (for older style 1.0-proxies) C) CONNECT HTTP request over proxy: - "Host: [name]:[port]" - "Proxy-Connection: Keep-alive"
2005-05-11 17:52:59 +08:00
Proxy-Connection: Keep-Alive
more auth tests
2003-08-12 16:19:23 +08: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-23 10:25:56 +08:00
</testcase>
Reference in New Issue Copy Permalink