From 82412f218fe6809288c718c5b43b9675eb2856f5 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 3 Jul 2008 08:47:53 +0000 Subject: Phil Blundell provided a fix for libcurl's treatment of unexpected 1xx response codes. Previously libcurl would hang on such occurances. I added test case 1033 to verify. --- tests/data/test1033 | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 tests/data/test1033 (limited to 'tests/data/test1033') diff --git a/tests/data/test1033 b/tests/data/test1033 new file mode 100644 index 000000000..62b03dfb2 --- /dev/null +++ b/tests/data/test1033 @@ -0,0 +1,60 @@ +# +# This case with an unexpected 1xx response used to cause a "hang" before the fix +# got 7.19.0 + + + +HTTP +HTTP GET + + + +# +# Server-side + + +HTTP/1.1 102 unexpected huh?! + +HTTP/1.1 200 OK +Date: Thu, 09 Nov 2010 14:49:00 GMT +Server: test-server/fake +Last-Modified: Tue, 13 Jun 2000 12:10:00 GMT +ETag: "21025-dc7-39462498" +Accept-Ranges: bytes +Content-Length: 6 +Connection: close +Content-Type: text/html +Funny-head: yesyes + +-foo- + + + +# +# Client-side + + +http + + +HTTP GET with 102 response! + + +http://%HOSTIP:%HTTPPORT/1033 + + + +# +# Verify data after the test has been "shot" + + +^User-Agent:.* + + +GET /1033 HTTP/1.1 +Host: %HOSTIP:%HTTPPORT +Accept: */* + + + + -- cgit v1.2.3