13 HTTP/1.1 301 Redirect swsclose
\r
14 Date: Thu, 29 Jul 2008 14:49:00 GMT
\r
15 Server: test-server/fake
\r
16 Location: data/10510002.txt?coolsite=yes
\r
22 HTTP/1.1 100 Continue
\r
24 HTTP/1.1 200 Followed here fine swsclose
\r
25 Date: Thu, 29 Jul 2008 14:49:00 GMT
\r
26 Server: test-server/fake
\r
29 If this is received, the location following worked
32 HTTP/1.1 301 Redirect swsclose
\r
33 Date: Thu, 29 Jul 2008 14:49:00 GMT
\r
34 Server: test-server/fake
\r
35 Location: data/10510002.txt?coolsite=yes
\r
39 HTTP/1.1 100 Continue
\r
41 HTTP/1.1 200 Followed here fine swsclose
\r
42 Date: Thu, 29 Jul 2008 14:49:00 GMT
\r
43 Server: test-server/fake
\r
46 If this is received, the location following worked
56 HTTP PUT with Location: following
59 http://%HOSTIP:%HTTPPORT/want/1051 -L -T log/test1051.txt
61 <file name="log/test1051.txt">
74 # Verify data after the test has been "shot"
80 # The primary reason libcurl sends the data part twice in this test is that
81 # the test HTTP server is blocking until it has read the entire request,
82 # including the full request-body before it responds. So in this test the
83 # server says 301 and 100 _after_ the entire PUT body has been sent.
86 PUT /want/1051 HTTP/1.1
\r
87 Host: %HOSTIP:%HTTPPORT
\r
90 Expect: 100-continue
\r
101 PUT /want/data/10510002.txt?coolsite=yes HTTP/1.1
\r
102 Host: %HOSTIP:%HTTPPORT
\r
105 Expect: 100-continue
\r