curl/tests/data/test305

# Server-side
<reply>
<data>
</data>
</reply>

# Client-side
<client>
<features>
SSL
</features>
<server>
https
</server>
 <name>
insecure HTTPS without permission
 </name>
 <command>
https://%HOSTIP:%HTTPPORT/want/305 --cacert moooo
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
</protocol>
<errorcode>
60
</errorcode>
</verify>
new tests 2002-08-30 06:58:37 -04:00			`# Server-side`
			`<reply>`
			`<data>`
			`</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>`
new tests 2002-08-30 06:58:37 -04:00			`<name>`
			`insecure HTTPS without permission`
			`</name>`
			`<command>`
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			`https://%HOSTIP:%HTTPPORT/want/305 --cacert moooo`
new tests 2002-08-30 06:58:37 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
new tests 2002-08-30 06:58:37 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`</protocol>`
			`<errorcode>`
			`60`
			`</errorcode>`
			`</verify>`