mirror/curl
2
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2025-04-18 16:30:45 +08:00
Code Issues Packages Projects Releases Wiki Activity
curl/tests/data/test483

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

67 lines
1.3 KiB
Plaintext
Raw Permalink Normal View History

cookie: parse only the exact expire date The date parser function is very forgiving and skips most "irrelevant" characters in its hunt for a date to figure out. Therefore it is important to make sure the date string is properly null terminated so that it does not accidentally parse a piece of whatever text follows after the date. Add test483: test (overly) long expire dates in cookies Closes #15709
2024-12-10 12:39:57 +01:00
<testcase>
<info>
<keywords>
HTTP
HTTP GET
cookies
</keywords>
</info>
#
# Server-side
<reply>
<data crlf="yes">
HTTP/1.1 200 OK
Set-Cookie: name=value; expires=Fri Feb 13 11:56:27 GMT 2132
Set-Cookie: name2=value; expires=Fri Feb 13 11:56:27 ; 2132
Set-Cookie: name3=value; expires=Fri Feb 13 11:56:27 ...................................................GMT 2132
Set-Cookie: name4=value; expires=Fri Feb 13 11:56:27 ....................................................GMT 2132
Accept-Ranges: bytes
Content-Length: 6
Connection: close
-foo-
</data>
</reply>
#
# Client-side
<client>
<server>
http
</server>
<features>
test483: require cookie support The test fails with `--disable-cookies`. Closes https://github.com/curl/curl/pull/15876
2024-12-31 10:35:40 +01:00
cookies
cookie: parse only the exact expire date The date parser function is very forgiving and skips most "irrelevant" characters in its hunt for a date to figure out. Therefore it is important to make sure the date string is properly null terminated so that it does not accidentally parse a piece of whatever text follows after the date. Add test483: test (overly) long expire dates in cookies Closes #15709
2024-12-10 12:39:57 +01:00
large-time
</features>
<name>
HTTP cookies with long expire dates
</name>
<command>
http://%HOSTIP:%HTTPPORT/%TESTNUMBER -c %LOGDIR/c%TESTNUMBER
</command>
</client>
#
# Verify data after the test has been "shot"
<verify>
<protocol crlf="yes">
GET /%TESTNUMBER HTTP/1.1
Host: %HOSTIP:%HTTPPORT
User-Agent: curl/%VERSION
Accept: */*
</protocol>
<file name="%LOGDIR/c%TESTNUMBER" mode="text">
# Netscape HTTP Cookie File
# https://curl.se/docs/http-cookies.html
# This file was generated by libcurl! Edit at your own risk.
127.0.0.1 FALSE / FALSE 0 name4 value
cookie: cap expire times to 400 days The pending cookie RFC update (currently known as 6265bis draft-19) says Let cookie-age-limit be the maximum age of the cookie (which name of Max-Age and an attribute-value of expiry-time. SHOULD be 400 days or less. This change makes received cookies over the wire get capped to 400 days. It does not cap the expiry date of cookies loaded from file. It does this by rounding the expire time to a even minute. This, to allow the test suite to do the same and have a chance to get the same number for stable testing without requiring a debug build. The test script generates TWO numbers in the output file for each %days[] used in the input test file, and the function that subsequently compares and verifies output is fine with *either* of the two numbers. This is done so that if the test case is generated the second immediately before curl runs, that updated expiry number is also deemed okay. It still checks for an exact match of either number. Closes #15937
2025-01-08 10:19:26 +01:00
127.0.0.1 FALSE / FALSE %days[400] name3 value
cookie: parse only the exact expire date The date parser function is very forgiving and skips most "irrelevant" characters in its hunt for a date to figure out. Therefore it is important to make sure the date string is properly null terminated so that it does not accidentally parse a piece of whatever text follows after the date. Add test483: test (overly) long expire dates in cookies Closes #15709
2024-12-10 12:39:57 +01:00
127.0.0.1 FALSE / FALSE 0 name2 value
cookie: cap expire times to 400 days The pending cookie RFC update (currently known as 6265bis draft-19) says Let cookie-age-limit be the maximum age of the cookie (which name of Max-Age and an attribute-value of expiry-time. SHOULD be 400 days or less. This change makes received cookies over the wire get capped to 400 days. It does not cap the expiry date of cookies loaded from file. It does this by rounding the expire time to a even minute. This, to allow the test suite to do the same and have a chance to get the same number for stable testing without requiring a debug build. The test script generates TWO numbers in the output file for each %days[] used in the input test file, and the function that subsequently compares and verifies output is fine with *either* of the two numbers. This is done so that if the test case is generated the second immediately before curl runs, that updated expiry number is also deemed okay. It still checks for an exact match of either number. Closes #15937
2025-01-08 10:19:26 +01:00
127.0.0.1 FALSE / FALSE %days[400] name value
cookie: parse only the exact expire date The date parser function is very forgiving and skips most "irrelevant" characters in its hunt for a date to figure out. Therefore it is important to make sure the date string is properly null terminated so that it does not accidentally parse a piece of whatever text follows after the date. Add test483: test (overly) long expire dates in cookies Closes #15709
2024-12-10 12:39:57 +01:00
</file>
</verify>
</testcase>
Reference in New Issue Copy Permalink