moparisthebest/wget
1
0
Fork 0
mirror of https://github.com/moparisthebest/wget synced 2024-07-03 16:38:41 -04:00
Code Issues Releases Wiki Activity

[svn] Explain why rfc2109 and rfc2965 are ignored by Wget's cookie code.

Browse Source
This commit is contained in:
hniksic 2005-05-24 07:13:47 -07:00
parent 724e2f84be
commit 4b0ade0434
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
src/cookies.c
View File

@ -27,20 +27,20 @@ modify this file, you may extend this exception to your version of the
file, but you are not obligated to do so. If you do not wish to do file, but you are not obligated to do so. If you do not wish to do
so, delete this exception statement from your version. */ so, delete this exception statement from your version. */
/* Written by Hrvoje Niksic. Parts are loosely inspired by cookie /* Written by Hrvoje Niksic. Parts are loosely inspired by the
code submitted by Tomasz Wegrzanowski. cookie patch submitted by Tomasz Wegrzanowski.
Ideas for future work: This implements the client-side cookie support, as specified
(loosely) by Netscape's "preliminary specification", currently
available at:
* Implement limits on cookie-related sizes, such as max. cookie http://wp.netscape.com/newsref/std/cookie_spec.html
size, max. number of cookies, etc.
* Add more "cookie jar" methods, such as methods to iterate over rfc2109 is not supported because of its incompatibilities with the
stored cookies, to clear temporary cookies, to perform above widely-used specification. rfc2965 is entirely ignored,
intelligent auto-saving, etc. since popular client software doesn't implement it, and even the
sites that do send Set-Cookie2 also emit Set-Cookie for
* Support `Set-Cookie2' and `Cookie2' headers? Does anyone really compatibility. */
use them? */
#include <config.h> #include <config.h>