| Re: PEAR Auth package woes [message #178395 is a reply to message #178384] |
Wed, 13 June 2012 05:52   |
J.O. Aho
Messages: 194
Registered: September 2010
Karma:
|
Senior Member |
|
|
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
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]