| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081 |
- <testcase>
- <info>
- <keywords>
- HTTP
- HTTPS
- HTTP GET
- followlocation
- </keywords>
- </info>
- # Server-side
- <reply>
- <data>
- HTTP/1.1 301 This is a weirdo text message swsclose
- Date: Tue, 09 Nov 2010 14:49:00 GMT
- Server: test-server/fake
- Location: https://%HOSTIP:%HTTPSPORT/data/%TESTNUMBER0002.txt?coolsite=yes
- Connection: close
- This server reply is for testing a simple Location: following to HTTPS URL
- </data>
- <data2>
- HTTP/1.1 200 Followed here fine swsclose
- Date: Tue, 09 Nov 2010 14:49:00 GMT
- Server: test-server/fake
- Content-Length: 52
- If this is received, the location following worked
- </data2>
- <datacheck>
- HTTP/1.1 301 This is a weirdo text message swsclose
- Date: Tue, 09 Nov 2010 14:49:00 GMT
- Server: test-server/fake
- Location: https://%HOSTIP:%HTTPSPORT/data/%TESTNUMBER0002.txt?coolsite=yes
- Connection: close
- HTTP/1.1 200 Followed here fine swsclose
- Date: Tue, 09 Nov 2010 14:49:00 GMT
- Server: test-server/fake
- Content-Length: 52
- If this is received, the location following worked
- </datacheck>
- </reply>
- # Client-side
- <client>
- <features>
- SSL
- </features>
- <server>
- http
- https
- </server>
- <name>
- HTTP Location: redirect to HTTPS URL
- </name>
- <command>
- -k http://%HOSTIP:%HTTPPORT/want/%TESTNUMBER -L
- </command>
- </client>
- # Verify data after the test has been "shot"
- <verify>
- <protocol>
- GET /want/%TESTNUMBER HTTP/1.1
- Host: %HOSTIP:%HTTPPORT
- User-Agent: curl/%VERSION
- Accept: */*
- GET /data/%TESTNUMBER0002.txt?coolsite=yes HTTP/1.1
- Host: %HOSTIP:%HTTPSPORT
- User-Agent: curl/%VERSION
- Accept: */*
- </protocol>
- </verify>
- </testcase>
|