mirror/curl
2
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2024-11-21 01:16:58 +08:00
Code Issues Packages Projects Releases Wiki Activity
ab0fa55780
curl/tests/data/test31

123 lines
4.8 KiB
Plaintext
Raw Normal View History

Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools.
2007-01-23 10:25:56 +08:00
<testcase>
keywords added
2005-04-17 07:15:19 +08:00
<info>
<keywords>
HTTP
HTTP GET
cookies
cookiejar
</keywords>
</info>
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
modified to work fine with the new persistant connection working test suite HTTP server
2003-07-20 07:57:08 +08:00
Content-Length: 4
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
Content-Type: text/html
Funny-head: yesyes
modified to work with modified code
2003-05-01 01:16:25 +08:00
Set-Cookie: foobar=name; domain=anything.com; path=/ ; secure
extended and improved cookie testing
2002-07-30 06:21:37 +08:00
Set-Cookie:ismatch=this ; domain=127.0.0.1; path=/silly/
cookie parser: handle 'secure=' There are two keywords in cookie headers that don't follow the regular name=value style: secure and httponly. Still we must support that they are written like 'secure=' and then treat them as if they were written 'secure'. Test case 31 was much extended by Rob Ward to test this. Bug: http://curl.haxx.se/bug/view.cgi?id=3349227 Reported by: "gnombat"
2011-08-09 20:02:05 +08:00
Set-Cookie: sec1value=secure1 ; domain=127.0.0.1; path=/secure1/ ; secure
Set-Cookie: sec2value=secure2 ; domain=127.0.0.1; path=/secure2/ ; secure=
Set-Cookie: sec3value=secure3 ; domain=127.0.0.1; path=/secure3/ ; secure=
Set-Cookie: sec4value=secure4 ; secure=; domain=127.0.0.1; path=/secure4/ ;
Set-Cookie: sec5value=secure5 ; secure; domain=127.0.0.1; path=/secure5/ ;
Set-Cookie: sec6value=secure6 ; secure ; domain=127.0.0.1; path=/secure6/ ;
Set-Cookie: sec7value=secure7 ; secure ; domain=127.0.0.1; path=/secure7/ ;
Set-Cookie: sec8value=secure8 ; secure= ; domain=127.0.0.1; path=/secure8/ ;
Set-Cookie: secure=very1 ; secure=; domain=127.0.0.1; path=/secure9/;
Set-Cookie: httpo1=value1 ; domain=127.0.0.1; path=/p1/; httponly
Set-Cookie: httpo2=value2 ; domain=127.0.0.1; path=/p2/; httponly=
Set-Cookie: httpo3=value3 ; httponly; domain=127.0.0.1; path=/p3/;
Set-Cookie: httpo4=value4 ; httponly=; domain=127.0.0.1; path=/p4/;
Set-Cookie: httponly=myvalue1 ; domain=127.0.0.1; path=/p4/; httponly
Set-Cookie: httpandsec=myvalue2 ; domain=127.0.0.1; path=/p4/; httponly; secure
Set-Cookie: httpandsec2=myvalue3; domain=127.0.0.1; path=/p4/; httponly=; secure
Set-Cookie: httpandsec3=myvalue4 ; domain=127.0.0.1; path=/p4/; httponly; secure=
Set-Cookie: httpandsec4=myvalue5 ; domain=127.0.0.1; path=/p4/; httponly=; secure=
Set-Cookie: httpandsec5=myvalue6 ; domain=127.0.0.1; path=/p4/; secure; httponly=
Set-Cookie: httpandsec6=myvalue7 ; domain=127.0.0.1; path=/p4/; secure=; httponly=
Set-Cookie: httpandsec7=myvalue8 ; domain=127.0.0.1; path=/p4/; secure; httponly
Set-Cookie: httpandsec8=myvalue9; domain=127.0.0.1; path=/p4/; secure=; httponly
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
Set-Cookie: partmatch=present; domain=127.0.0.1 ; path=/;
extended and improved cookie testing
2002-07-30 06:21:37 +08:00
Set-Cookie:eat=this; domain=moo.foo.moo;
new field1 functionality testing too
2002-02-26 21:18:39 +08:00
Set-Cookie: eat=this-too; domain=.foo.moo;
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
Set-Cookie: nodomainnovalue
Year 2038 has its own problems (32 bit integer overflow). So cookie expiration date is lowered to expire at most in 2035.
2007-02-05 10:38:25 +08:00
Set-Cookie: nodomain=value; expires=Fri Feb 2 11:56:27 GMT 2035
modified to work with modified code
2003-05-01 01:16:25 +08:00
Set-Cookie: novalue; domain=reallysilly
Year 2038 has its own problems (32 bit integer overflow). So cookie expiration date is lowered to expire at most in 2035.
2007-02-05 10:38:25 +08:00
Set-Cookie: test=yes; domain=foo.com; expires=Sat Feb 2 11:56:27 GMT 2030
Set-Cookie: test2=yes; domain=se; expires=Sat Feb 2 11:56:27 GMT 2030
- Niklas Angebrand made the cookie support in libcurl properly deal with the "HttpOnly" feature introduced by Microsoft and apparently also supported by Firefox: http://msdn2.microsoft.com/en-us/library/ms533046.aspx . HttpOnly is now supported when received from servers in HTTP headers, when written to cookie jars and when read from existing cookie jars.
2008-01-31 20:21:57 +08:00
Set-Cookie: magic=yessir; path=/silly/; HttpOnly
- Dima Barsky made the curl cookie parser accept cookies even with blank or unparsable expiry dates and then treat them as session cookies - previously libcurl would reject cookies with a date format it couldn't parse. Research shows that the major browser treat such cookies as session cookies. I modified test 8 and 31 to verify this.
2009-10-26 02:15:14 +08:00
Set-Cookie: blexp=yesyes; domain=.0.0.1; domain=.0.0.1; expiry=totally bad;
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
boo
</data>
</reply>
# Client-side
<client>
Each test case now specifies which server(s) it needs, without relying on the test number.
2003-05-01 04:25:39 +08:00
<server>
http
</server>
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
<name>
HTTP with weirdly formatted cookies and cookiejar storage
</name>
Force the time zone to GMT in the cookie tests in case the user is using one of the so-called 'right' time zones that take into account leap seconds, which causes the tests to fail (as reported by Daniel Black in bug report #1745964).
2007-07-11 06:27:16 +08:00
# Explicitly set the time zone to a known good one, in case the user is
# using one of the 'right' zones that take into account leap seconds
# which causes the cookie expiry times to be different.
<setenv>
TZ=GMT
</setenv>
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
<command>
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script.
2004-09-08 16:08:38 +08:00
http://%HOSTIP:%HTTPPORT/we/want/31 -b none -c log/jar31.txt
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
</command>
A minor "syntax error" in numerous test files corrected
2005-01-26 05:45:03 +08:00
</client>
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /we/want/31 HTTP/1.1
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-15 03:32:31 +08:00
Host: %HOSTIP:%HTTPPORT
Modified the default HTTP Accept: header to only be Accept: */*
2004-02-09 20:46:41 +08:00
Accept: */*
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
</protocol>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => &amp; ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools.
2007-01-23 10:25:56 +08:00
<file name="log/jar31.txt" mode="text">
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
# Netscape HTTP Cookie File
cookies: change the URL in the cookie jar file header
2012-07-03 17:27:45 +08:00
# http://curl.haxx.se/docs/http-cookies.html
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
# This file was generated by libcurl! Edit at your own risk.
modified to work with modified code
2003-05-01 01:16:25 +08:00
.127.0.0.1 TRUE /silly/ FALSE 0 ismatch this
cookie parser: handle 'secure=' There are two keywords in cookie headers that don't follow the regular name=value style: secure and httponly. Still we must support that they are written like 'secure=' and then treat them as if they were written 'secure'. Test case 31 was much extended by Rob Ward to test this. Bug: http://curl.haxx.se/bug/view.cgi?id=3349227 Reported by: "gnombat"
2011-08-09 20:02:05 +08:00
.127.0.0.1 TRUE /secure1/ TRUE 0 sec1value secure1
.127.0.0.1 TRUE /secure2/ TRUE 0 sec2value secure2
.127.0.0.1 TRUE /secure3/ TRUE 0 sec3value secure3
.127.0.0.1 TRUE /secure4/ TRUE 0 sec4value secure4
.127.0.0.1 TRUE /secure5/ TRUE 0 sec5value secure5
.127.0.0.1 TRUE /secure6/ TRUE 0 sec6value secure6
.127.0.0.1 TRUE /secure7/ TRUE 0 sec7value secure7
.127.0.0.1 TRUE /secure8/ TRUE 0 sec8value secure8
.127.0.0.1 TRUE /secure9/ TRUE 0 secure very1
#HttpOnly_.127.0.0.1 TRUE /p1/ FALSE 0 httpo1 value1
#HttpOnly_.127.0.0.1 TRUE /p2/ FALSE 0 httpo2 value2
#HttpOnly_.127.0.0.1 TRUE /p3/ FALSE 0 httpo3 value3
#HttpOnly_.127.0.0.1 TRUE /p4/ FALSE 0 httpo4 value4
#HttpOnly_.127.0.0.1 TRUE /p4/ FALSE 0 httponly myvalue1
#HttpOnly_.127.0.0.1 TRUE /p4/ TRUE 0 httpandsec myvalue2
#HttpOnly_.127.0.0.1 TRUE /p4/ TRUE 0 httpandsec2 myvalue3
#HttpOnly_.127.0.0.1 TRUE /p4/ TRUE 0 httpandsec3 myvalue4
#HttpOnly_.127.0.0.1 TRUE /p4/ TRUE 0 httpandsec4 myvalue5
#HttpOnly_.127.0.0.1 TRUE /p4/ TRUE 0 httpandsec5 myvalue6
#HttpOnly_.127.0.0.1 TRUE /p4/ TRUE 0 httpandsec6 myvalue7
#HttpOnly_.127.0.0.1 TRUE /p4/ TRUE 0 httpandsec7 myvalue8
#HttpOnly_.127.0.0.1 TRUE /p4/ TRUE 0 httpandsec8 myvalue9
modified to work with modified code
2003-05-01 01:16:25 +08:00
.127.0.0.1 TRUE / FALSE 0 partmatch present
Year 2038 has its own problems (32 bit integer overflow). So cookie expiration date is lowered to expire at most in 2035.
2007-02-05 10:38:25 +08:00
127.0.0.1 FALSE /we/want/ FALSE 2054030187 nodomain value
- Niklas Angebrand made the cookie support in libcurl properly deal with the "HttpOnly" feature introduced by Microsoft and apparently also supported by Firefox: http://msdn2.microsoft.com/en-us/library/ms533046.aspx . HttpOnly is now supported when received from servers in HTTP headers, when written to cookie jars and when read from existing cookie jars.
2008-01-31 20:21:57 +08:00
#HttpOnly_127.0.0.1 FALSE /silly/ FALSE 0 magic yessir
- Dima Barsky made the curl cookie parser accept cookies even with blank or unparsable expiry dates and then treat them as session cookies - previously libcurl would reject cookies with a date format it couldn't parse. Research shows that the major browser treat such cookies as session cookies. I modified test 8 and 31 to verify this.
2009-10-26 02:15:14 +08:00
.0.0.1 TRUE /we/want/ FALSE 0 blexp yesyes
test 31: "HTTP with weirdly formatted cookies and cookiejar storage"
2002-02-26 21:09:46 +08:00
</file>
</verify>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => &amp; ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools.
2007-01-23 10:25:56 +08:00
</testcase>
Reference in New Issue Copy Permalink