[pLog-svn] session cookie domain, is it needed?

[Jon Daley]

 	I think it is correct behavior to set the path so cookies don't 
collide with other apps installed in other programs.  (I have had trouble 
in the past with multiple lifetype installations stomping on each other's 
session info).
 	But, I don't understand what the problem is.  The cookie should be 
set with the path that the URL is using, and so shouldn't be affected by 
custom URLs or plain, etc.  Can you give more examples of what the URLs 
are, ie. you show the custom URL that doesn't work, but if you hit the 
plain URL switch, what would the url be?  I would expect it to be 
/index.php?stuff

So, the cookie path for this installation should be /, but if I install 
LT in a subdirectory, the cookie should have that path info in it.

Perhaps we are calculating the path information incorrectly?

On Sun, 4 Feb 2007, Oscar Renalias wrote:

> I just noticed that if custom URLs are enabled, the comment form is
> not able to detect if there is a user logged in or not. The problem
> is that the session cookie was created with a path like for example /
> lifetype-1.2 while the current path because of the permalink is /blog/
> test-blog/2007/02/03/test-post and the browser won't send the cookie.
>
> Does anybody remember why we set a path for the cookie? Setting a
> path of "/" is the only way to get this working again.
> _______________________________________________
> pLog-svn mailing list
> pLog-svn at devel.lifetype.net
> http://limedaley.com/mailman/listinfo/plog-svn
>

-- 
Jon Daley
http://jon.limedaley.com/

Satan only gives you the seeds for sin, not the whole plant.
He leaves the growing up to us.