113498266Sopenharmony_ci<testcase> 213498266Sopenharmony_ci<info> 313498266Sopenharmony_ci<keywords> 413498266Sopenharmony_ciFTP 513498266Sopenharmony_ciNLST 613498266Sopenharmony_ciPORT 713498266Sopenharmony_ci</keywords> 813498266Sopenharmony_ci</info> 913498266Sopenharmony_ci# Server-side 1013498266Sopenharmony_ci<reply> 1113498266Sopenharmony_ci<servercmd> 1213498266Sopenharmony_ciREPLY NLST 550 Have a taste on this! 1313498266Sopenharmony_ci</servercmd> 1413498266Sopenharmony_ci<data> 1513498266Sopenharmony_ci</data> 1613498266Sopenharmony_ci</reply> 1713498266Sopenharmony_ci 1813498266Sopenharmony_ci# Client-side 1913498266Sopenharmony_ci<client> 2013498266Sopenharmony_ci<server> 2113498266Sopenharmony_ciftp 2213498266Sopenharmony_ci</server> 2313498266Sopenharmony_ci<name> 2413498266Sopenharmony_ciFTP NLST dir list with weird reply code, using PORT 2513498266Sopenharmony_ci</name> 2613498266Sopenharmony_ci<command> 2713498266Sopenharmony_ciftp://%HOSTIP:%FTPPORT/ -P - -l 2813498266Sopenharmony_ci</command> 2913498266Sopenharmony_ci</client> 3013498266Sopenharmony_ci 3113498266Sopenharmony_ci# Verify data after the test has been "shot" 3213498266Sopenharmony_ci<verify> 3313498266Sopenharmony_ci<errorcode> 3413498266Sopenharmony_ci19 3513498266Sopenharmony_ci</errorcode> 3613498266Sopenharmony_ci# Strip all valid kinds of PORT and EPRT that curl can send 3713498266Sopenharmony_ci<strip> 3813498266Sopenharmony_ci^PORT \d{1,3},\d{1,3},\d{1,3},\d{1,3},\d{1,3},\d{1,3} 3913498266Sopenharmony_ci^EPRT \|1\|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\|\d{1,5}\| 4013498266Sopenharmony_ci</strip> 4113498266Sopenharmony_ci<protocol> 4213498266Sopenharmony_ciUSER anonymous 4313498266Sopenharmony_ciPASS ftp@example.com 4413498266Sopenharmony_ciPWD 4513498266Sopenharmony_ciPORT 127,0,0,1,243,212 4613498266Sopenharmony_ciTYPE A 4713498266Sopenharmony_ciNLST 4813498266Sopenharmony_ciQUIT 4913498266Sopenharmony_ci</protocol> 5013498266Sopenharmony_ci</verify> 5113498266Sopenharmony_ci</testcase> 52