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
3e820fbf25
curl/tests/data/test63

54 lines
856 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-22 21:25:56 -05:00
<testcase>
keywords added
2005-04-22 17:59:08 -04:00
<info>
<keywords>
HTTP
HTTP GET
HTTP proxy
HTTP proxy Basic auth
</keywords>
</info>
the proxy environment variables now may contain user name and password
2003-05-19 09:09:41 -04:00
# Server-side
<reply>
<data>
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-19 19:57:08 -04:00
HTTP/1.1 200 OK swsclose
tests: fixup several tests missing CRs and modified %hostip lib556/test556: use a real HTTP version to make test reuse more convenient make sure the weekday in Date headers matches the date test61: replace stray "^M" (5e 4d) at the end of a cookie with a '^M' (0d) Gets the test working with external proxies like Privoxy again. Closes #6463
2020-02-28 09:00:03 -05:00
Date: Tue, 09 Nov 2010 14:49:00 GMT
the proxy environment variables now may contain user name and password
2003-05-19 09:09:41 -04:00
Content-Type: text/html
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
Content-Length: 26
the proxy environment variables now may contain user name and password
2003-05-19 09:09:41 -04:00
the content would go here
</data>
</reply>
# Client-side
<client>
<server>
http
</server>
<name>
HTTP with proxy authorization set in environment
</name>
<setenv>
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 04:08:38 -04:00
http_proxy=http://fake:user@%HOSTIP:%HTTPPORT/
the proxy environment variables now may contain user name and password
2003-05-19 09:09:41 -04:00
</setenv>
<command>
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738
2021-03-12 11:38:26 -05:00
http://we.want.that.site.com/%TESTNUMBER
the proxy environment variables now may contain user name and password
2003-05-19 09:09:41 -04:00
</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>
A minor "syntax error" in numerous test files corrected
2005-01-25 16:45:03 -05:00
</client>
the proxy environment variables now may contain user name and password
2003-05-19 09:09:41 -04:00
# Verify data after the test has been "shot"
<verify>
<protocol>
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738
2021-03-12 11:38:26 -05:00
GET http://we.want.that.site.com/%TESTNUMBER HTTP/1.1
the proxy environment variables now may contain user name and password
2003-05-19 09:09:41 -04:00
Host: we.want.that.site.com
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
Proxy-Authorization: Basic ZmFrZTp1c2Vy
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: */*
Revert "Proxy-Connection: stop sending this header by default" This reverts commit 113f04e664b16b944e64498a73a4dab990fe9a68.
2016-08-16 02:36:04 -04:00
Proxy-Connection: Keep-Alive
the proxy environment variables now may contain user name and password
2003-05-19 09:09:41 -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