Download new version from Cookiepie 1.0.0

—-

The page isn’t redirecting properly.

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

This problem can sometimes be caused by disabling or refusing to accept cookies.
—-

CookieSwap still works, but I prefer the CookiePie interface. Alas.

Great Extension. Simply wonderful. I just wanted to point out a few problems, however.
1) If I have a tab open with CookiePie turned on, and I rearrange the tabs, such that the ordinal number (the order) of the CookiePie tab changes, the CookiePie settings no longer work. If I move the CookiePie tab itself, the CookiePie icon disappears. If I move/delete other tabs, it remains, but again, if the order changes, the settings are lost. Restoring the order of the CookiePie tab, by adding or moving the tabs (and toggling CookiePie on, if necessary), appears to restore the session. So from what I can see, the CookiePie information is stored based on the ordinal number, and this ordinal number is not updated when tabs are moved or deleted.

2) I have been unable to determine the exact circumstances under which this occurs, but while trying to log into SquirrelMail, I recieve less than consistent separation of cookie management between CooliePie-enabled and non-CookiePie-enabled sites. If I start with a closed browser and log into two sites, one with CookiePie, and another without, the separation appears to work. However, at some point subsequent to opening the browser, the is separation no longer complete. What do I mean by “no longer complete”? The symptoms are described below:

a) Tab 1 is logged into SquirrelMail without CookiePie on one email account (e.g. account1@mydomain.com) .
b) Tab 2 is opened, cookie pie is enabled, and an attempt to connect to the logged in (non-CookiePie) session fails (as it should fail). I click the link to go to the login screen.
c) After logging in with a different account (e.g. account2@mydomain.com) to SquirrelMail, I access the first account’s inbox (account1@mydomain.com), even though the login credentials entered were for account2@mydomain.com.
d) It should be noted that subequent log-out log-in process result in the same behavior. Once CookiePie attains this state, the only way to reset it is to close the browser completely and restart it.

I’m using FF 2.0.0.7 and CookiePie 0.5.5

Once again, thanks for a great extension.

Eric

I see this mentioned on the to-do list. Just wanted to give it some priority if possible. Many thanks

Alan

can I please ask how does this extension compare / contrast with CookieSwap :-
https://addons.mozilla.org/en-US/firefox/addon/3255

I’d be grateful if someone familiar with both could give a quick overview of the differences.

thanks a lot,
Lee
England

can I please ask how does this extension compare / contrast with CookieSwap :-
https://addons.mozilla.org/en-US/firefox/addon/3255

I’d be grateful if someone familiar with both could give a quick overview of the differences.

thanks a lot,
Lee
England

For example: I have Tab A with Cookiepie turned Off which uses cookie A. I also have a tab with Cookiepie On which uses cookie B. When I use javascript on Tab B to read the cookie, it returns cookie A (the wrong one).

This is a major issue for us, since we use javascript to pass the cookie when we do an ajax request. This is required for protection against cross-site request forgery when programming ajax methods (referred to as the “double-submit” method of guarding against CSRF).

Please let me know if you can confirm this bug (I’m using FF 2.0.0.2 on ubuntu linux) and if you will be able to release a new version of your extension to address this.

Thanks very much,
Dan