<feed xmlns='http://www.w3.org/2005/Atom'>
<title>curl/tests/data/test1151, branch gemini-meta</title>
<subtitle>cURL mirror with patches applied
</subtitle>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/'/>
<entry>
<title>cookies: support creation-time attribute for cookies</title>
<updated>2018-08-31T12:11:37+00:00</updated>
<author>
<name>Daniel Gustafsson</name>
<email>daniel@yesql.se</email>
</author>
<published>2018-08-28T09:28:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=e2ef8d6fa11b2345e10b89db525920f2a0d5fd79'/>
<id>e2ef8d6fa11b2345e10b89db525920f2a0d5fd79</id>
<content type='text'>
According to RFC6265 section 5.4, cookies with equal path lengths
SHOULD be sorted by creation-time (earlier first). This adds a
creation-time record to the cookie struct in order to make cookie
sorting more deterministic. The creation-time is defined as the
order of the cookies in the jar, the first cookie read fro the
jar being the oldest. The creation-time is thus not serialized
into the jar. Also remove the strcmp() matching in the sorting as
there is no lexicographic ordering in RFC6265. Existing tests are
updated to match.

Closes #2524
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
According to RFC6265 section 5.4, cookies with equal path lengths
SHOULD be sorted by creation-time (earlier first). This adds a
creation-time record to the cookie struct in order to make cookie
sorting more deterministic. The creation-time is defined as the
order of the cookies in the jar, the first cookie read fro the
jar being the oldest. The creation-time is thus not serialized
into the jar. Also remove the strcmp() matching in the sorting as
there is no lexicographic ordering in RFC6265. Existing tests are
updated to match.

Closes #2524
</pre>
</div>
</content>
</entry>
<entry>
<title>cookie tests: treat files as text</title>
<updated>2018-08-23T11:11:20+00:00</updated>
<author>
<name>Marcel Raad</name>
<email>Marcel.Raad@teamviewer.com</email>
</author>
<published>2018-08-23T11:11:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=387e85efd08d9a7d184c9fd37cba61110728e511'/>
<id>387e85efd08d9a7d184c9fd37cba61110728e511</id>
<content type='text'>
Fixes test failures because of wrong line endings on Windows.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fixes test failures because of wrong line endings on Windows.
</pre>
</div>
</content>
</entry>
<entry>
<title>cookies: reject oversized cookies</title>
<updated>2017-09-18T20:55:50+00:00</updated>
<author>
<name>Daniel Stenberg</name>
<email>daniel@haxx.se</email>
</author>
<published>2017-09-17T22:55:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/curl/commit/?id=2bc230de63bd7da197280a69d84972b61455cd18'/>
<id>2bc230de63bd7da197280a69d84972b61455cd18</id>
<content type='text'>
... instead of truncating them.

There's no fixed limit for acceptable cookie names in RFC 6265, but the
entire cookie is said to be less than 4096 bytes (section 6.1). This is
also what browsers seem to implement.

We now allow max 5000 bytes cookie header. Max 4095 bytes length per
cookie name and value. Name + value together may not exceed 4096 bytes.

Added test 1151 to verify

Bug: https://curl.haxx.se/mail/lib-2017-09/0062.html
Reported-by: Kevin Smith

Closes #1894
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
... instead of truncating them.

There's no fixed limit for acceptable cookie names in RFC 6265, but the
entire cookie is said to be less than 4096 bytes (section 6.1). This is
also what browsers seem to implement.

We now allow max 5000 bytes cookie header. Max 4095 bytes length per
cookie name and value. Name + value together may not exceed 4096 bytes.

Added test 1151 to verify

Bug: https://curl.haxx.se/mail/lib-2017-09/0062.html
Reported-by: Kevin Smith

Closes #1894
</pre>
</div>
</content>
</entry>
</feed>
