tedd wrote:
Tedd,
The cookie is being set on the www.xn--ovg.com domain. The cookie is
being read on xn--ovg.com domain. This is perceived to be a security
risk, so the cookie isn't sent.
David
???
Interesting -- the first time it's read correctly and the second
time it's a security risk -- how doe that work?
tedd
www.xn--ovg.com is not the same domain name as xn--ovg.com and the
browser stores cookies against the domain so when the second request
goes through on the second domain it does not get passed the cookie
set on the first domain. If you want more Google for this topic -
it's been covered to death in the past both here and pretty much
everywhere else.
-Stut
Ahhh, I see now. Regardless of if it's been beat to death, or not, my
question wasn't IF there was a difference between a domain w/o "www",
but rather WHY my cookie wasn't working as I expected.
I wasn't aware of the sporadic "www" prefix addition to my url's at
that site. I didn't notice that sometimes my url's would have the
"www" prefix and other times they wouldn't. When they did have the
"www", the cookie would work and when they didn't, it wouldn't work.
It was confusing, at least for me.
In any event, many thanks to all for pointing that difference out to
me. I feel a lot better about cookies now.
Thanks.
tedd
--
--------------------------------------------------------------------------------
http://sperling.com/
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
