curl/tests/data/test567

<testcase>

#Informational
<info>
<keywords>
RTSP
OPTIONS
</keywords>
</info>

# Server-side
<reply>
<data>
RTSP/1.0 200 OK
Server: RTSPD/libcurl-test
CSeq: 1
Public: DESCRIBE, OPTIONS, SETUP, TEARDOWN, PLAY, PAUSE
Curl-Private: swsclose
</data>
</reply>

# Client-Side
<client>
<server>
rtsp
</server>
<tool>
lib567
</tool>

<name>
simple RTSP OPTIONS command
</name>
<command>
rtsp://%HOSTIP:%RTSPPORT/567
</command>
</client>

<verify>
<protocol>
OPTIONS rtsp://%HOSTIP:%RTSPPORT/567 RTSP/1.0
CSeq: 1
User-Agent: test567
Test-Number: 567

</protocol>
</verify>

</testcase>
Chris Conroy provided first RTSP tests 2010-01-27 23:58:03 -05:00			`<testcase>`

			`#Informational`
			`<info>`
			`<keywords>`
			`RTSP`
			`OPTIONS`
			`</keywords>`
			`</info>`

			`# Server-side`
			`<reply>`
			`<data>`
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-01-31 18:52:08 -05:00			`RTSP/1.0 200 OK`
			`Server: RTSPD/libcurl-test`
			`CSeq: 1`
			`Public: DESCRIBE, OPTIONS, SETUP, TEARDOWN, PLAY, PAUSE`
			`Curl-Private: swsclose`
Chris Conroy provided first RTSP tests 2010-01-27 23:58:03 -05:00			`</data>`
			`</reply>`

			`# Client-Side`
			`<client>`
			`<server>`
			`rtsp`
			`</server>`
			`<tool>`
			`lib567`
			`</tool>`

			`<name>`
			`simple RTSP OPTIONS command`
			`</name>`
			`<command>`
			`rtsp://%HOSTIP:%RTSPPORT/567`
			`</command>`
			`</client>`

			`<verify>`
			`<protocol>`
			`OPTIONS rtsp://%HOSTIP:%RTSPPORT/567 RTSP/1.0`
			`CSeq: 1`
			`User-Agent: test567`
			`Test-Number: 567`

			`</protocol>`
			`</verify>`

			`</testcase>`