generic-library/curl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
ed285ae5c9
curl/tests/data/test522

61 lines
772 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 03:25:56 +01:00
<testcase>
Olivier reported that even though he used CURLOPT_PORT, libcurl clearly still used the default port. He was right. I fixed the problem and added the test cases 521, 522 and 523 to verify the fix.
2005-04-18 21:41:04 +02:00
<info>
<keywords>
HTTP
HTTP GET
CURLOPT_PORT
</keywords>
</info>
#
# Server-side
<reply>
Always use nocheck="yes" for consistency
2009-01-07 22:57:26 +01:00
<data nocheck="yes">
testsuite: changed HTTP and RTSP header line-endings to CRLF According to RFC 2616 and RFC 2326 individual protocol elements, like headers and except the actual content, are terminated by using CRLF. Therefore the test data files for these protocols need to contain mixed line-endings if the actual protocol elements use CRLF while the file uses LF.
2014-02-01 00:52:08 +01:00
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT
ETag: "21025-dc7-39462498"
Accept-Ranges: bytes
Content-Length: 6
Olivier reported that even though he used CURLOPT_PORT, libcurl clearly still used the default port. He was right. I fixed the problem and added the test cases 521, 522 and 523 to verify the fix.
2005-04-18 21:41:04 +02:00
hello
</data>
</reply>
#
# Client-side
<client>
<server>
http
</server>
<tool>
lib521
</tool>
<name>
HTTP GET with CURLOPT_PORT
</name>
<command>
http://%HOSTIP/522 %HTTPPORT
</command>
</client>
#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /522 HTTP/1.1
Authorization: Basic eHh4Onl5eQ==
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 21:32:31 +02:00
Host: %HOSTIP:%HTTPPORT
Olivier reported that even though he used CURLOPT_PORT, libcurl clearly still used the default port. He was right. I fixed the problem and added the test cases 521, 522 and 523 to verify the fix.
2005-04-18 21:41:04 +02:00
Accept: */*
</protocol>
testsuite: use binary output mode for custom curl test tools Do not try to convert line-endings to CRLF on Windows by setting stdout to binary mode, just like the curl tool does if --ascii is not specified. This should prevent corrupted stdout line-ending output like CRCRLF. In order to make the previously naive text-aware tests work with binary mode on Windows, text-mode is disabled for them if it is not actually part of the test case and line-endings are corrected.
2014-02-01 00:58:58 +01:00
<stdout>
Olivier reported that even though he used CURLOPT_PORT, libcurl clearly still used the default port. He was right. I fixed the problem and added the test cases 521, 522 and 523 to verify the fix.
2005-04-18 21:41:04 +02:00
hello
</stdout>
</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 03:25:56 +01:00
</testcase>
Reference in New Issue Copy Permalink