[pmwiki-users] cookie problem with Firefox

[Hans]

Friday, January 13, 2006, 1:42:25 PM, Patrick wrote:
> Oh, I just noticed that your previous message indicated that
> you had already fixed this on your site.  Hmmm.

> Can you re-state exactly what problems you're encountering?
> If you can demonstrate the problem on pmwiki.org, that would
> be even more helpful.  :-)

okay, i try. But it is bizarre...
It happens on pmwiki.org and on my own site using Firefox 1.5 on
Windows XP.

I have been browsing pmwiki.org in the past with the gemini skin, and
lately with the triad skin.
to narrow down the causes i clear firefox's cache.
I remove all cookies with pmwiki.org.
I reload the page, or enter new to a page on pmwiki.org.
It comes up with triad skin.
Viewing firefox cookies i see all the old cookie's i just removed still
there.
Now i go to Cookbook/Cookbook. Triad skin is still showing.
I do ?setskin=gemini. (there is a convenient button to do that on the
rightbar). Result is pmwiki skin showing.
Doing ?setskin=gemini does not change the pmwiki skin.
Clicking on the Cookbook group link reloads the page with triad skin.
Back to viewing the cookies:
i se now two setskin cookies, both set to gemini, but with different
hosts: www.pmwiki.org and .pmwiki.org
I remove them both.
A forced reload (Ctrl-F5) opens the page with pmwiki skin.
?setskin=gemini or ?setskin=triad does not do anything.
Viewing the cookies again i notice now two cookies again, with
different host names as before, but now one is set to gemini and one
to triad.
I clear all pmwiki.org cookies.
I clear the cache.
I reload the page, typing Cookbook/Cookbook as url.
It opens with pmwiki skin.
I look at the cookies: no cookies for pmwiki.org.
I add ?setskin=triad to the url.
The page opens with triad skin.
i go to othe rpages, all open with triad skin.
I go back to Cookbook/Cookbook; it opens in pmwiki skin.
I look at the cookies: two setskin cookies are present again with
different host names again, as before, both  set to triad.
I sent this email, utterly bewildered. some bad case of mistaken
cookie settings?
Sorry about this long report, but i needed to show each step.


Best, 
~Hans