-----Original Message-----
From:	Kehvan M. Zydhek [SMTP:kehvan(at)zydhek.net]
Sent:	Sunday, April 30, 2000 6:12 PM
To:	David Clapper; hwg-techniques(at)hwg.org
Subject:	Re: One Cookie/Multiple Domains

<clip>

Like I said, it's possible, but doing so is bad practice, no matter the
reason.

</clip>

Well, I would dispute that-there are very valid reasons, like the site =
merely has multiple domain names, but is essentially the same business.  =
I personally have two domains, one is for my web development business, =
and one is for my applications development business.  There has been =
some crossover between the sites, and I refuse to send separate bills to =
the same client.  Not only does it increase the amount of work I have to =
do, it increases the number of invoices they have to pay, and I would =
have double the accounting that would otherwise be necessary.

Now, if you are using Perl to generate cookies, it's actually not that =
difficult:  just set two cookies, one for each domain.  Cookies support =
being set so that a different domain receives them.  The only warning I =
attach to cookie use is that you should never put any information into a =
cookie which could possibly mean anything to anyone in the outside =
world, like credit card numbers.  Account numbers are fine...just as =
long as an account number is insufficient to do anything to that =
account, like, you need the account number AND a password to change =
account details.

I personally use a multi-character alphanumeric string which is a =
primary key in a database which "unlocks" account details.  It's =
virtually impossible to guess, and a potential abuser would still need =
to know the username and password.

• Web Designer Courses
• Off the Shelf Training Courses

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA