|
|
Posted by Rik on 02/06/07 18:58
Tom <tom@to.com> wrote:
> On Tue, 6 Feb 2007 13:21:07 -0500, hman wrote...
>>
>> The DNS is working correctly according to the client where this is
>> happening.
>>
>> What should I use for the full domain in this case. I can't find a good
>> explanation on use of the domain when setting cookies.
>>
>> I need to cookies to work for SQL1, 10.1.1.100 AND for
>> statuspage.cosite.com.
>>
>> Thanks,
>> Harry Hambrick
>
>
> From my understanding a cookie can only be generated from a server in its
> domain, since there would be problems with outside sides trying to forge
> cookies
> for another domain. You might not be able to use "SQL1, 10.1.1.100 and
> statuspage.cosite.com." in one cookie and may need to generate three
> separate
> cookies.
@OP Pffffft... crossposting.....evil.. mmkay?
Rik wrote in comp.lang.php:
"> As far as the cookies go, do I need to specify the domain and path in
the
> cookies for them to work with both the domain and the machine name?
Normally, no, server and path default to the current. Users connecting by
one address should have no trouble continuing using that address, and the
cookies it sets. Switching would make your cookies invalid for that
ip/name/server, as they've been set for the other. The browser just won't
send them. You can _try_ to set a cookie for another domain/ip/machine
name, but this would cookie would be declined by the standard settings of
most modern browsers. "
Moral of the story: either allow all users to stay on their current
address/server, or enforce one immediately at the beginning, possibly
using a 301.
--
Rik Wasmus
Navigation:
[Reply to this message]
|