curl/tests/data/test306

<testcase>
<info>
<keywords>
HTTPS
HTTP GET
</keywords>
</info>

#
# Server-side
<reply>
<data>
No headers at all, just data swsclose

Let's get

a little

so that

we

have

some

test

data to

verify
</data>
</reply>

#
# Client-side
<client>
<features>
SSL
</features>
<server>
https
</server>
 <name>
HTTPS GET, receive no headers only data!
 </name>
 <command>
-k https://%HOSTIP:%HTTPSPORT/306 --http0.9
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
GET /306 HTTP/1.1
Host: %HOSTIP:%HTTPSPORT
User-Agent: curl/%VERSION
Accept: */*

</protocol>
</verify>
</testcase>
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>`
Added key words to all SSL-using tests so they can be skipped if necessary. Removed a few unnecessary requires SSL statements. 2008-02-08 21:08:34 -05:00			`<info>`
			`<keywords>`
			`HTTPS`
			`HTTP GET`
			`</keywords>`
			`</info>`

request a page from HTTPS but get no headers 2002-09-13 06:56:23 -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			`No headers at all, just data swsclose`
request a page from HTTPS but get no headers 2002-09-13 06:56:23 -04:00
			`Let's get`

			`a little`

			`so that`

			`we`

			`have`

			`some`

			`test`

			`data to`

			`verify`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
properly mark tests as requiring feature 'SSL' 2005-01-30 07:53:05 -05:00			`<features>`
			`SSL`
			`</features>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-04-30 16:25:39 -04:00			`<server>`
			`https`
			`</server>`
request a page from HTTPS but get no headers 2002-09-13 06:56:23 -04:00			`<name>`
			`HTTPS GET, receive no headers only data!`
			`</name>`
			`<command>`
http: added options for allowing HTTP/0.9 responses Added CURLOPT_HTTP09_ALLOWED and --http0.9 for this purpose. For now, both the tool and library allow HTTP/0.9 by default. docs/DEPRECATE.md lays out the plan for when to reverse that default: 6 months after the 7.64.0 release. The options are added already now so that applications/scripts can start using them already now. Fixes #2873 Closes #3383 2018-12-17 09:46:56 -05:00			`-k https://%HOSTIP:%HTTPSPORT/306 --http0.9`
request a page from HTTPS but get no headers 2002-09-13 06:56:23 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
request a page from HTTPS but get no headers 2002-09-13 06:56:23 -04:00
			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`GET /306 HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPSPORT`
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: /`
request a page from HTTPS but get no headers 2002-09-13 06:56:23 -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. & => & ). 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>`