various new cookie tests with a custom Host: header set

test130  test131  test132  test133  test134 test135 test403 test305 \

test49 test50 test51 test52 test53 test54 test55 test56 \

test500 test501 test502 test503 test504 test136 test57 test137 test138 \

test58 test139 test140 test141 test59 test60

test58 test139 test140 test141 test59 test60 test61

# Server-side

<reply>

<data>

HTTP/1.1 200 OK

Date: Thu, 09 Nov 2010 14:49:00 GMT

Server: test-server/fake

Content-Type: text/html

Funny-head: yesyes

Set-Cookie: test=yes; domain=foo.com; expires=Tue Feb 1 11:56:27 MET 2007

Set-Cookie: test2=yes; domain=host.foo.com; expires=Tue Feb 1 11:56:27 MET 2007

Set-Cookie: test3=maybe; domain=foo.com; path=/moo; secure

Set-Cookie: test4=no; domain=nope.foo.com; path=/moo; secure

Set-Cookie: test5=name; domain=anything.com; path=/ ; secure

boo

</data>

</reply>

# Client-side

<client>

 <name>

HTTP with various cookies and custom Host:

 </name>

 <command>

http://%HOSTIP:%HOSTPORT/we/want/61 -c log/jar61.txt -H "Host: www.host.foo.com"

</command>

</test>

# Verify data after the test has been "shot"

<verify>

<strip>

^User-Agent:.*

</strip>

<protocol>

GET /we/want/61 HTTP/1.1

Pragma: no-cache

Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*

Host: www.host.foo.com

</protocol>

<file name="log/jar61.txt">

# Netscape HTTP Cookie File

# http://www.netscape.com/newsref/std/cookie_spec.html

# This file was generated by libcurl! Edit at your own risk.

.127.0.0.1	TRUE	/silly/	FALSE	0	ismatch	this

.127.0.0.1	TRUE	/	FALSE	0	partmatch	present

127.0.0.1	FALSE	/we/want/	FALSE	1391252187	nodomain	value

</file>

</verify>