curl/tests/data/test660

<testcase>
<info>
<keywords>
IMAP
CONNECT_ONLY
</keywords>
</info>

# Client-side
<client>
<server>
imap
</server>
<tool>
lib597
</tool>
 <name>
IMAP CONNECT_ONLY option
 </name>

<command>
imap://%HOSTIP:%IMAPPORT/660
</command>

</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
A001 CAPABILITY
A002 LOGOUT
</protocol>
</verify>
</testcase>
test660: verify CONNECT_ONLY with IMAP which basically just makes sure LOGOUT is not issued on disconnect 2019-04-19 23:33:02 +02:00			`<testcase>`
			`<info>`
			`<keywords>`
			`IMAP`
			`CONNECT_ONLY`
			`</keywords>`
			`</info>`

			`# Client-side`
			`<client>`
			`<server>`
			`imap`
			`</server>`
			`<tool>`
			`lib597`
			`</tool>`
			`<name>`
			`IMAP CONNECT_ONLY option`
			`</name>`

			`<command>`
			`imap://%HOSTIP:%IMAPPORT/660`
			`</command>`

			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`A001 CAPABILITY`
lib: pass in 'struct Curl_easy ' to most functions ... in most cases instead of 'struct connectdata ' but in some cases in addition to. - We mostly operate on transfers and not connections. - We need the transfer handle to log, store data and more. Everything in libcurl is driven by a transfer (the CURL * in the public API). - This work clarifies and separates the transfers from the connections better. - We should avoid "conn->data". Since individual connections can be used by many transfers when multiplexing, making sure that conn->data points to the current and correct transfer at all times is difficult and has been notoriously error-prone over the years. The goal is to ultimately remove the conn->data pointer for this reason. Closes #6425 2021-01-08 17:58:15 +01:00			`A002 LOGOUT`
test660: verify CONNECT_ONLY with IMAP which basically just makes sure LOGOUT is not issued on disconnect 2019-04-19 23:33:02 +02:00			`</protocol>`
			`</verify>`
			`</testcase>`