curl/tests/data/test894

<testcase>
<info>
<keywords>
POP3
Clear Text
RETR
</keywords>
</info>

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

#
# Client-side
<client>
<server>
pop3
</server>
 <name>
POP3 with CR in username
 </name>
 <command>
pop3://user%0dFRIGGING_cmd:secret@%HOSTIP:%POP3PORT/%TESTNUMBER
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
# malformed URL
<errorcode>
3
</errorcode>
</verify>
</testcase>
ftp: remove superfluous checking for crlf in user or pwd ... as this is already done much earlier in the URL parser. Also add test case 894 that verifies that pop3 with an encodedd CR in the user name is rejected. Closes #4887 2020-02-06 11:36:53 +01:00			`<testcase>`
			`<info>`
			`<keywords>`
			`POP3`
			`Clear Text`
			`RETR`
			`</keywords>`
			`</info>`

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

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`pop3`
			`</server>`
			`<name>`
			`POP3 with CR in username`
			`</name>`
			`<command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 17:38:26 +01:00			`pop3://user%0dFRIGGING_cmd:secret@%HOSTIP:%POP3PORT/%TESTNUMBER`
ftp: remove superfluous checking for crlf in user or pwd ... as this is already done much earlier in the URL parser. Also add test case 894 that verifies that pop3 with an encodedd CR in the user name is rejected. Closes #4887 2020-02-06 11:36:53 +01:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`# malformed URL`
			`<errorcode>`
			`3`
			`</errorcode>`
			`</verify>`
			`</testcase>`