Two commits ago, we fixed a bug where the connction would be closed
prematurely after a HEAD. Now I added connection-monitor to test 48 and
added a second HEAD and make sure that both are sent over the same
connection.
This triggered a failure before the bug fix and now works. Will help us
avoid a future regression of this kind.
#
# Server-side
<reply>
+<servercmd>
+connection-monitor
+</servercmd>
<data>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
-Connection: close
</data>
</reply>
HTTP with -d and -G and -I
</name>
<command>
--d "foo=moo&moo=poo" http://%HOSTIP:%HTTPPORT/48 -G -I
+-d "foo=moo&moo=poo" http://%HOSTIP:%HTTPPORT/48 -G -I http://%HOSTIP:%HTTPPORT/48
</command>
</client>
Host: %HOSTIP:%HTTPPORT\r
Accept: */*\r
\r
+HEAD /48?foo=moo&moo=poo HTTP/1.1\r
+Host: %HOSTIP:%HTTPPORT\r
+Accept: */*\r
+\r
+[DISCONNECT]
</protocol>
</verify>
</testcase>