Re: session file umask

http://qs321.pair.com?node_id=735790

in reply to session file umask

Pretty unlikely to be a permissions problem if you're not seeing anything in the error log. I'd look at the cookies being generated - do they have the correct domain? Are they being sent back to the server on subsequent requests?

-sam

Comment on Re: session file umask

Replies are listed 'Best First'.
Re^2: session file umask by ksublondie (Friar) on Jan 12, 2009 at 20:41 UTC
Interesting observation...I hadn't thought of the cookies. It looks like the cookies have the right domain. Is the folder path important? How do I tell if they are being sent back to the server? thanks	[reply]
Re^3: session file umask by samtregar (Abbot) on Jan 12, 2009 at 20:55 UTC
Yes, the path setting on the cookie matters - it tells the browser which part of the site the cookie applies to. Set it wrong and you won't get your cookie back! I mainly use two tools for debugging cookie problem - first, Firefox with the Web Developer addon. This gives you a screen where you can see what cookies are set and all their parameters. Failing that I pull out the big gun - wireshark. It's a network-level protocol examiner and you can use it to see exactly what the client and server are actually saying to each other. The learning curve is steep but sometimes you really need to see what's actually on the wire to solve a problem. -sam	[reply]
Re^4: session file umask by ksublondie (Friar) on Jan 12, 2009 at 22:14 UTC
Forgive me for any stupid questions... Do I set the path to the file session location or my script location? LOVE the web developer plugin...it's soooooo valuable in getting my layout & css just right. Never thought to use it with the cookies. I'll play with that and the wireshark and see where that goes...	[reply]
Re^5: session file umask by samtregar (Abbot) on Jan 13, 2009 at 19:50 UTC

In Section Seekers of Perl Wisdom