aboutsummaryrefslogtreecommitdiff
path: root/tests/data/test1033
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2008-07-03 08:47:53 +0000
committerDaniel Stenberg <daniel@haxx.se>2008-07-03 08:47:53 +0000
commit82412f218fe6809288c718c5b43b9675eb2856f5 (patch)
treefbd25f4a9a4be0c1879c9cc29643caebc9cc574f /tests/data/test1033
parent7c648782bc7c97be81c619acd8598c38b59c5832 (diff)
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.
Diffstat (limited to 'tests/data/test1033')
-rw-r--r--tests/data/test103360
1 files changed, 60 insertions, 0 deletions
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
+<testcase>
+<info>
+<keywords>
+HTTP
+HTTP GET
+</keywords>
+</info>
+
+#
+# Server-side
+<reply>
+<data>
+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-
+</data>
+</reply>
+
+#
+# Client-side
+<client>
+<server>
+http
+</server>
+ <name>
+HTTP GET with 102 response!
+ </name>
+ <command>
+http://%HOSTIP:%HTTPPORT/1033
+</command>
+</client>
+
+#
+# Verify data after the test has been "shot"
+<verify>
+<strip>
+^User-Agent:.*
+</strip>
+<protocol>
+GET /1033 HTTP/1.1
+Host: %HOSTIP:%HTTPPORT
+Accept: */*
+
+</protocol>
+</verify>
+</testcase>