113498266Sopenharmony_ci<testcase> 213498266Sopenharmony_ci<info> 313498266Sopenharmony_ci<keywords> 413498266Sopenharmony_ciHTTP 513498266Sopenharmony_ciHTTP GET 613498266Sopenharmony_ci</keywords> 713498266Sopenharmony_ci</info> 813498266Sopenharmony_ci 913498266Sopenharmony_ci# Server-side 1013498266Sopenharmony_ci<reply> 1113498266Sopenharmony_ci<data> 1213498266Sopenharmony_ciHTTP/1.0 401 BAD BOY 1313498266Sopenharmony_ciServer: swsclose 1413498266Sopenharmony_ciContent-Type: text/html 1513498266Sopenharmony_ci 1613498266Sopenharmony_ciThis contains a response code >= 400, so curl shouldn't display this. Even 1713498266Sopenharmony_cithough it's a response code that triggers authentication, we're not using 1813498266Sopenharmony_ciauthentication so we should still fail. 1913498266Sopenharmony_ci</data> 2013498266Sopenharmony_ci</reply> 2113498266Sopenharmony_ci 2213498266Sopenharmony_ci# Client-side 2313498266Sopenharmony_ci<client> 2413498266Sopenharmony_ci<server> 2513498266Sopenharmony_cihttp 2613498266Sopenharmony_ci</server> 2713498266Sopenharmony_ci<name> 2813498266Sopenharmony_ciHTTP GET with an error code that might trick authentication 2913498266Sopenharmony_ci</name> 3013498266Sopenharmony_ci<command> 3113498266Sopenharmony_cihttp://%HOSTIP:%HTTPPORT/%TESTNUMBER 3213498266Sopenharmony_ci</command> 3313498266Sopenharmony_ci</client> 3413498266Sopenharmony_ci 3513498266Sopenharmony_ci# Verify data after the test has been "shot" 3613498266Sopenharmony_ci<verify> 3713498266Sopenharmony_ci<protocol> 3813498266Sopenharmony_ciGET /%TESTNUMBER HTTP/1.1 3913498266Sopenharmony_ciHost: %HOSTIP:%HTTPPORT 4013498266Sopenharmony_ciUser-Agent: curl/%VERSION 4113498266Sopenharmony_ciAccept: */* 4213498266Sopenharmony_ci 4313498266Sopenharmony_ci</protocol> 4413498266Sopenharmony_ci</verify> 4513498266Sopenharmony_ci</testcase> 46