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
0f645adc95
curl/tests/data/test530

84 lines
1.3 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-23 10:25:56 +08:00
<testcase>
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
<info>
<keywords>
HTTP
Multiple pipelines and limiting the number of connections. Introducing a number of options to the multi interface that allows for multiple pipelines to the same host, in order to optimize the balance between the penalty for opening new connections and the potential pipelining latency. Two new options for limiting the number of connections: CURLMOPT_MAX_HOST_CONNECTIONS - Limits the number of running connections to the same host. When adding a handle that exceeds this limit, that handle will be put in a pending state until another handle is finished, so we can reuse the connection. CURLMOPT_MAX_TOTAL_CONNECTIONS - Limits the number of connections in total. When adding a handle that exceeds this limit, that handle will be put in a pending state until another handle is finished. The free connection will then be reused, if possible, or closed if the pending handle can't reuse it. Several new options for pipelining: CURLMOPT_MAX_PIPELINE_LENGTH - Limits the pipeling length. If a pipeline is "full" when a connection is to be reused, a new connection will be opened if the CURLMOPT_MAX_xxx_CONNECTIONS limits allow it. If not, the handle will be put in a pending state until a connection is ready (either free or a pipe got shorter). CURLMOPT_CONTENT_LENGTH_PENALTY_SIZE - A pipelined connection will not be reused if it is currently processing a transfer with a content length that is larger than this. CURLMOPT_CHUNK_LENGTH_PENALTY_SIZE - A pipelined connection will not be reused if it is currently processing a chunk larger than this. CURLMOPT_PIPELINING_SITE_BL - A blacklist of hosts that don't allow pipelining. CURLMOPT_PIPELINING_SERVER_BL - A blacklist of server types that don't allow pipelining. See the curl_multi_setopt() man page for details.
2013-02-15 18:50:45 +08:00
pipelining
Added multi keyword
2008-08-27 04:11:12 +08:00
multi
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
</keywords>
</info>
Added multi keyword
2008-08-27 04:11:12 +08:00
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
# Server-side
<reply>
Dmitry Kurochkin fixed test case 530 (pipelining)
2008-01-19 18:14:45 +08:00
<data1>
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 07:52:08 +08:00
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Content-Length: 47
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
file contents should appear once for each file
Dmitry Kurochkin fixed test case 530 (pipelining)
2008-01-19 18:14:45 +08:00
</data1>
<data2>
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 07:52:08 +08:00
HTTP/1.1 200 OK
Dmitry Kurochkin fixed test case 530 (pipelining)
2008-01-19 18:14:45 +08:00
</data2>
<data3>
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 07:52:08 +08:00
Date: Thu, 09 Nov 2010 14:49:00 GMT
Dmitry Kurochkin fixed test case 530 (pipelining)
2008-01-19 18:14:45 +08:00
</data3>
<data4>
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 07:52:08 +08:00
Server: test-server/fake
Content-Length: 47
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
file contents should appear once for each file
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 07:52:08 +08:00
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Content-Length: 47
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
file contents should appear once for each file
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 07:52:08 +08:00
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Content-Length: 47
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
file contents should appear once for each file
Dmitry Kurochkin fixed test case 530 (pipelining)
2008-01-19 18:14:45 +08:00
</data4>
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
</reply>
# Client-side
<client>
<server>
http
</server>
<tool>
lib530
</tool>
<name>
HTTP GET using pipelining
</name>
<command>
http://%HOSTIP:%HTTPPORT/path/530
</command>
</client>
# Verify data after the test has been "shot"
<verify>
<protocol>
Dmitry Kurochkin fixed test case 530 (pipelining)
2008-01-19 18:14:45 +08:00
GET /path/5300001 HTTP/1.1
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
Host: %HOSTIP:%HTTPPORT
Accept: */*
Dmitry Kurochkin fixed test case 530 (pipelining)
2008-01-19 18:14:45 +08:00
GET /path/5300002 HTTP/1.1
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
Host: %HOSTIP:%HTTPPORT
Accept: */*
Dmitry Kurochkin fixed test case 530 (pipelining)
2008-01-19 18:14:45 +08:00
GET /path/5300003 HTTP/1.1
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
Host: %HOSTIP:%HTTPPORT
Accept: */*
Dmitry Kurochkin fixed test case 530 (pipelining)
2008-01-19 18:14:45 +08:00
GET /path/5300004 HTTP/1.1
test 530 is the first ever HTTP pipelining test for libcurl
2006-09-08 19:56:56 +08:00
Host: %HOSTIP:%HTTPPORT
Accept: */*
</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