I'm the author of "bug:21" and i've added a bunch of data posted to that thread. Seems like the potential cookie problem is limited to safari on MacOS but not to other browsers/OSes (I posted several different trial combos).

Is this still going to be looked at? Or is this not going to be tackled. I've been watching the bug report site for a while in hopes that it can be fixed…

We'll make a test suite that users will be able to visit in order to check potential problems with their configuration. Then we can collect some data to later improve.

Ok, in the meantime do you have any idea how I might edit the configuration on safari to try and resolve this problem? I am not that versed in "cookie" bugs, so I am not sure what to try (other than to switch my browser…)

Another instance of bug:13. This also occurs on sign in to an existing private site as well as creation of a new site. Systems that I have seen display the problem are…

• Firefox 3.5.8, Ubuntu 9.10
• Firefox 3.6.3, Ubuntu 9.10
• Android 2.1 running on an HTC Desire (Nexus 1)

Systems that do not display the problem…

• Firefox 3.6.3, Ubuntu 8.04
• Firefox 3.0.5, Windows XP SP3 running within VirtualBox 3.1.6 on the same Ubuntu 9.10 machine that displays the problem
• Firefox 3.6.3, Windows XP SP3 running within VirtualBox 3.1.6 on the same Ubuntu 9.10 machine that displays the problem
• IE8, Windows XP SP3 running within VirtualBox 3.1.6 on the same Ubuntu 9.10 machine that displays the problem

In all cases where I experience problems I tried removing both normal and flash cookies. Obviously this forces a new sign in, but did not fix the issue.

In all cases apart from the HTC Desire the machines are directly connected to the internet via a broadband router. Data passes through several software firewalls, but no proxies. I have tried from several locations with the Ubuntu 9.10 machine with the same results.

I have not seen such looping behaviour before on any of these machines with other site's web applications. If you need me to conduct further tests please let me know.

Cheers

Ian

Meanwhile we have pushed a set of updates that should eliminate most problems with sessions and cookies. It appeared though that in most cases the session problems were caused by over-restrictive local network or ISP policy, e.g. filtering cookies, caching content and overriding our caching policy in http responses.

RE: bug 13. I experienced this for a new private site. Firefox went into the infinite loop. Internet Explorer on the same machine showed the site just fine. For me this fixed it in Firefox:
Tools-Options, Privacy tab, Exceptions button to the "accept cookies from sites" check box. Add wdfiles.com with status Allow to the exceptions. I first added wikidot.com to the exceptions but still had the infinite loop. It stopped when I added wdfiles.com (so I don't know if you need both added).

Well it didn't work for me unfortunately. I'm using Firefox. Any additional ideas? Thanks !