Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "J.O. Aho" <user@example.net>
Newsgroups: comp.lang.php
Subject: Re: PEAR Auth package woes
Date: Wed, 13 Jun 2012 07:52:02 +0200
Lines: 22
Message-ID: <a3qo42FpgjU1@mid.individual.net>
References: <eli$1206112021@qz.little-neck.ny.us> <jr62rc$db7$1@dont-email.me> <eli$1206121328@qz.little-neck.ny.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net 215mPWtLzTgHPfa3z39j+gRR8LSFj8ohM6japlPgzVZ851BopTYDDMcD1x7RS2rYjk
Cancel-Lock: sha1:dxi5vl2lJ3UBEvJlA5rHSopbhlQ=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120518 Firefox/12.0 SeaMonkey/2.9.1
In-Reply-To: <eli$1206121328@qz.little-neck.ny.us>
Xref: csiph.com comp.lang.php:6317

Eli the Bearded wrote:

> I've been using this setup just fine for years, but now I want a small
> password protected area. Using the PEAR Auth package I've created it,
> but cookies set on web-server-1.colo-1.internal.name do not work on
> web-server-2.colo-1.internal.name or web-server-3.colo-2.internal.name.

I haven't used the PEAR Auth package, but the problem is your cookies, as each 
has their own subdomain, which makes machine A can't read machine B's cookie, 
and machines from Colo1 can't read cookies from Colo2.

You need to see to that the PEAR Auth will be using internal.name as the 
domain name.

Until you have fixed that, there is no way you will get it to work.
I suggest you submit the patch upstream when you have fixed it, so someone 
else who wants to use PEAR Auth in the same way as you, can do it too.


-- 

   //Aho