guest2013-1
guest
- Joined
- Aug 22, 2003
- Messages
- 19,800
And no, not the yummy chocolate ones...
I'm busy with a secure site running on SSL.
www.acidrazor.co.za has the login that sets cookies for secure.acidrazor.co.za
I set the domain in the cookie itself, so www.acidrazor.co.za wouldn't have access to secure.acidrazor.co.za's cookies and "secure" is true.
However, the cookie isn't set at all (or appears not to be set)
If I do ".acidrazor.co.za" as the domain, then it works. But for both domains (I currently have secure:false because I don't have the SSL installed yet)
I read the RFC states the cookie has to have two dots ".something.com" (as an example, and can't be set to "something.com")
Could it be that the 3rd dot for "co.za" is the problem when setting this?
Any idears?
I'm busy with a secure site running on SSL.
www.acidrazor.co.za has the login that sets cookies for secure.acidrazor.co.za
I set the domain in the cookie itself, so www.acidrazor.co.za wouldn't have access to secure.acidrazor.co.za's cookies and "secure" is true.
However, the cookie isn't set at all (or appears not to be set)
If I do ".acidrazor.co.za" as the domain, then it works. But for both domains (I currently have secure:false because I don't have the SSL installed yet)
I read the RFC states the cookie has to have two dots ".something.com" (as an example, and can't be set to "something.com")
Could it be that the 3rd dot for "co.za" is the problem when setting this?
Any idears?