Cookie

[Daan]

I have a website that is accessible (at least from our local campus
network) by four different ways:

1) the full url: http://campuslaan37.student.utwente.nl/
2) the short url: http://campuslaan37/
3) an alias: http://cam37.student.utwente.nl/
4) the short alias: http://cam37/

I use cookies to save and set some preferences etc. However, if you
surf from e.g. (1) to (3), it is treated as an entirely different
site, and nothing that was stored in the cookie applies anymore.

Is there a way to set the cookie, such that it immediately applies
to all the possible URLs to access the site?

Thanks in advance,

--
Daan

[Alvaro G Vicario]

*** Daan wrote/escribió (Tue, 17 Aug 2004 11:54:48 +0200):

Is there a way to set the cookie, such that it immediately applies
to all the possible URLs to access the site?

setcookie() has a parameter called domain ("the domain that the cookie is
available"). Then it explains:

"To make the cookie available on all subdomains of example.com then you'd
set it to '.example.com'. The . is not required but makes it compatible
with more browsers. Setting it to www.example.com will make the cookie
only available in the www subdomain."

This doesn't exactly apply to your case since your URLs don't have a "tail"
in common. However, I suppose you could use setcookie() to set the cookie
several times, one for each domain. You could write a function to make it
easier:

function mysetcookie($name, $value='', $expire='', $path='', $secure=''){
$aliases=array(
'campuslaan37.student.utwente.nl',
'campuslaan37',
'am37.student.utwente.nl',
'cam37'
);

foreach($aliases as $domain){
setcookie($name, $value, $expire, $path, $domain, $secure);
}
}

Be aware that I didn't test the code. It probably needs to handle empty
parameters differently.

--
-- Álvaro G. Vicario - Burgos, Spain
-- Questions sent to my mailbox will be billed ;-)
--

[L�ʻie Techie]

On Tue, 17 Aug 2004 12:10:16 +0200, Alvaro G Vicario wrote:

*** Daan wrote/escribió (Tue, 17 Aug 2004 11:54:48 +0200):

Is there a way to set the cookie, such that it immediately applies to
all the possible URLs to access the site?

setcookie() has a parameter called domain ("the domain that the cookie is
available"). Then it explains:

"To make the cookie available on all subdomains of example.com then you'd
set it to '.example.com'. The . is not required but makes it compatible
with more browsers. Setting it to www.example.com will make the cookie
only available in the www subdomain."

This doesn't exactly apply to your case since your URLs don't have a
"tail" in common. However, I suppose you could use setcookie() to set the
cookie several times, one for each domain. You could write a function to
make it easier:

For security reasons, browsers will not set cookies which do not match a
different domain than where the page was served. In this case, you might
get away with setting the cookie's domain to ".student.utwente.pl" which
will include campuslaan37 and cam37.

HTH,
La'ie Techie

[steve]

"Lie Techie" wrote:

On Tue, 17 Aug 2004 12:10:16 +0200, Alvaro G Vicario wrote:

*** Daan wrote/escribió (Tue, 17 Aug 2004 11:54:48 +0200):

Is there a way to set the cookie, such that it immediately

applies

to all the possible URLs to access the site?
setcookie() has a parameter called domain ("the domain that the

cookie is

available"). Then it explains:

"To make the cookie available on all subdomains of example.com then

you’d

set it to ’.example.com’. The . is not required but

makes it compatible

with more browsers. Setting it to www.example.com will make the

cookie

only available in the www subdomain."

This doesn’t exactly apply to your case since your URLs

don’t have a

"tail" in common. However, I suppose you could use setcookie()

to set the

cookie several times, one for each domain. You could write a function to

make it easier:

For security reasons, browsers will not set cookies which do not

match a
different domain than where the page was served. In this case, you
might
get away with setting the cookie’s domain to
".student.utwente.pl" which
will include campuslaan37 and cam37.

HTH,
La’ie Techie

If nothing else works, you can always redirect the subdomain to the
real domain. There is a slight delay for the user and some refershing,
but at least your cookie info are available to the user.

--
http://www.dbForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbForumz.com/PHP-Cookie-ftopict140317.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbForumz.com/eform.php?p=470472