Bugs item #3404326, was opened at 2011-09-05 18:32
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3404326&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Pending
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Michael Brooks (sitewatch)
>Assigned to: Daniel Stenberg (bagder)
Summary: COOKIELIST interface inconsistancy

Initial Comment:
Using libCurl there are two ways to set a cookie. If curl encounters a cookie "Set-Cookie:" http header, or by using setopt(COOKIELIST) option. These two interfaces should be identical in every respect, but they are not!

In tis example i am using pyCurl on the client and php on the server.

<?php
setcookie("file","cookie_test.php");
?>
(This will work just fine) if i do a INFO_COOKIELIST i'll get this cookie value that was set by the server:
'localhost\tFALSE\t/\tFALSE\t0\tfile\tcookie_test.php'

If i take this EXACT same value and do a setopt:
self.c.setopt(pycurl.COOKIELIST,''localhost\tFALSE\t/\tFALSE\t0\tfile\tcookie_test.php']')
I'll get an exception:
TypeError: invalid arguments to setopt

BUGS!

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2011-09-05 19:41

Message:
Sorry, but that error is reported by the pycurl binding and not by libcurl,
which is a separate project so my advice is to report this bug to them. Or
perhaps write up a patch and suggest to them.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3404326&group_id=976
Received on 2011-09-05