[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] Re: Are Cookies Working Correctly in Lynx 2.8?

From: Owen Leibman
Subject: Re: [Lynx-dev] Re: Are Cookies Working Correctly in Lynx 2.8?
Date: Sat, 5 Mar 2011 23:57:40 -0800 (PST)

Thank you for your replay.
I believe that the file location is not just 'more information' - it is 

the behavior.
I have set up a test using the 2 attached files - setcookie.php and 
I have loaded them to domain directory cookietest.
To run the test, you need persistent cookies enabled.

1. lynx
2. Enter any value at all into the text form field.
3. Submit the form using the 'change cookie' button.
4. Follow the link to return to changecookie page; the cookie has apparently 
been changed correctly.
5. Quit lynx.
6. Repeat step 1 - notice that the cookie value is NOT being displayed in the 
text field.
Also notice that the cookie jar isn't empty - it still has the value you set 
with step 3 clearly visible,
but, equally clearly, that value isn't being used.

If you repeat these steps with Lynx 2.8.7, step 6 works as expected - it shows 

cookie value you set in step 3.
It also works as expected with all graphical browsers (e.g. Firefox) and other 
text browsers (e.g. w3m).
It is only with Lynx 2.8.8 that it is not working correctly.

----- Original Message ----
From: Thomas Dickey <address@hidden>
To: Owen Leibman <address@hidden>
Cc: address@hidden
Sent: Sat, March 5, 2011 7:02:48 AM
Subject: Re: [Lynx-dev] Re: Are Cookies Working Correctly in Lynx 2.8?

On Fri, 4 Mar 2011, Owen Leibman wrote:

> Resending this message. I have followed this mailing list since I sent it, 
> and 

>rare indeed has been the message which has not received a reply. This message 
>would seem to be the exception. Perhaps I just sent it a bad time, or perhaps 
>was because I erroneously specified 2.8 and 2.7 instead of 2.8..8 and 2.8.7. 

>the time I wrote the message, the lynx version which seemed not to be handling 
>cookies correctly was 2.8.8dev.3. I just tried the newest version 2.8.8dev.8 
>(dated Jan. 10, 2011), and it handles cookies in the same manner as 

>i.e. it associates the cookie (incorrectly in my opinion) with a specific file 
>name rather than directory name. Version 2.8.7 handles cookies as I expect it 
>should (and as all other browsers which I've tested do), associating the 

>with the directory name rather than a specific file name.

This is more information (the file-name vs directory name).

Perhaps it's related to my 2.8.8dev.2 change for Debian #460108.
(Just looking at the changelog, I don't see any other interesting
cookie changes since 2.8.7).

> --- On Wed, 8/25/10, Owen Leibman <address@hidden> wrote:
>> From: Owen Leibman <address@hidden>
>> Subject: Are Cookies Working Correctly in Lynx 2.8?
>> To: address@hidden
>> Date: Wednesday, August 25, 2010, 10:35 PM
>> Cookies don’t seem to be working as
>> I would expect for lynx-cur (2.8.something) on ubuntu
>> (10.4). The problem is demonstrated in the attached cookie
>> file – the complete file name which created the cookie is
>> stored rather than the directory, so other pages in that
>> directory do not see the cookie. After noticing this
>> problem, I did a complete build from source for 2.8.*, and
>> saw the same problem. When I did a complete build from
>> source for 2.7.*, there was no longer a problem – cookies
>> behaved as I expected. The first line of the cookies file
>> shows a 2.8 cookie incorrectly stored (from localhost); the
>> next 5 show a 2.7 cookie correctly stored; the final line
>> shows a 2.8 cookie incorrectly stored (from the web, just in
>> case there was something special about localhost which
>> triggered the error). I apologize for being a bit vague
>> about the release numbers; my daughter has taken that PC
>> away to school with her, so I don’t have immediate access
>> to it,
>>  but can get more exact details if needed.

-- Thomas E. Dickey


Attachment: changecookie.php
Description: Text document

Attachment: setcookie.php
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]