# Server-side <reply> <data> HTTP/1.1 301 This is a weirdo text message Date: Thu, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Location: /root/1870002.txt?coolsite=yes Connection: close This server reply is for testing a simple Location: following </data> <data2> HTTP/1.1 200 Followed here fine swsclose Date: Thu, 09 Nov 2010 14:49:00 GMT Server: test-server/fake If this is received, the location following worked </data2> <datacheck> HTTP/1.1 301 This is a weirdo text message Date: Thu, 09 Nov 2010 14:49:00 GMT Server: test-server/fake Location: /root/1870002.txt?coolsite=yes Connection: close HTTP/1.1 200 Followed here fine swsclose Date: Thu, 09 Nov 2010 14:49:00 GMT Server: test-server/fake If this is received, the location following worked </datacheck> </reply> # Client-side <client> <server> http </server> <name> HTTP redirect with bad host name separation and slash in parameters </name> <command> http://%HOSTIP:%HTTPPORT?oh=what-weird=test/187 -L </command> </client> # Verify data after the test has been "shot" <verify> <strip> ^User-Agent:.* </strip> <protocol> GET /?oh=what-weird=test/187 HTTP/1.1 Host: 127.0.0.1:%HTTPPORT Accept: */* GET /root/1870002.txt?coolsite=yes HTTP/1.1 Host: 127.0.0.1:%HTTPPORT Accept: */* </protocol> </verify>