HTTP HTTP PUT followlocation # Server-side HTTP/1.1 301 Redirect swsclose Date: Thu, 29 Jul 2008 14:49:00 GMT Server: test-server/fake Location: data/%TESTNUMBER0002.txt?coolsite=yes Content-Length: 0 Connection: close HTTP/1.1 100 Continue HTTP/1.1 200 Followed here fine swsclose Date: Thu, 29 Jul 2008 14:49:00 GMT Server: test-server/fake Content-Length: 51 If this is received, the location following worked HTTP/1.1 301 Redirect swsclose Date: Thu, 29 Jul 2008 14:49:00 GMT Server: test-server/fake Location: data/%TESTNUMBER0002.txt?coolsite=yes Content-Length: 0 Connection: close HTTP/1.1 100 Continue HTTP/1.1 200 Followed here fine swsclose Date: Thu, 29 Jul 2008 14:49:00 GMT Server: test-server/fake Content-Length: 51 If this is received, the location following worked # Client-side http HTTP PUT with Location: following http://%HOSTIP:%HTTPPORT/want/%TESTNUMBER -L -T log/test%TESTNUMBER.txt Weird file to upload for testing the PUT feature # Verify data after the test has been "shot" # The primary reason libcurl sends the data part twice in this test is that # the test HTTP server is blocking until it has read the entire request, # including the full request-body before it responds. So in this test the # server says 301 and 100 _after_ the entire PUT body has been sent. PUT /want/%TESTNUMBER HTTP/1.1 Host: %HOSTIP:%HTTPPORT User-Agent: curl/%VERSION Accept: */* Content-Length: 78 Expect: 100-continue Weird file to upload for testing the PUT feature PUT /want/data/%TESTNUMBER0002.txt?coolsite=yes HTTP/1.1 Host: %HOSTIP:%HTTPPORT User-Agent: curl/%VERSION Accept: */* Content-Length: 78 Expect: 100-continue Weird file to upload for testing the PUT feature