Last confirmation: 1.3.25-dev does indeed work fine.
I've got cookies flying everywhere!
Thanks guys!
-klm.
----- Original Message -----
From: "Ken Miller" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 07, 2002 3:45 PM
Subject: RE: Can't set multiple cookies?
> Yup, just confirmed it. 1.3.20 works fine, but .24 is busted.
>
> I'll try the latest CVS version.
>
> Thanks guys!
>
> -klm.
>
> -----Original Message-----
> From: Balazs Rauznitz [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 07, 2002 2:48 PM
> To: Dave Rolsky
> Cc: Ken Miller; [EMAIL PROTECTED]
> Subject: Re: Can't set multiple cookies?
>
>
> On Fri, Jun 07, 2002 at 12:32:56PM -0500, Dave Rolsky wrote:
> > On Fri, 7 Jun 2002, Ken Miller wrote:
> >
> > > Ok, so continuing down the path of a single sign-on system, I've
> completed a
> > > rough framework, and it works fine. However, I thought it might be
nice
> to
> > > segregate the various bits of information into different cookies.
> > > Unfortunately, setting multiple cookies doesn't seem to be working.
> Here
> > > are the outbound headers obtained via $r->as_string:
> > >
> > > Set-Cookie: ACS_UID=miller; path=/
> > > Set-Cookie: ACS_Test=blah; path=/
> > > Set-Cookie: ACS_Ticket=stuff; path=/
> > >
> > > on the next request, here's the Cookie header:
> > >
> > > Cookie: ACS_Ticket=stuff; RC_Creds=miller%2C
> >
> > I suspect you're using a 2-tier Apache setup with Apache 1.3.23 on the
> > frontend, right?
> >
> > This is a bug in mod_proxy with 1.3.23. I _think_ its fixed in 1.3.24.
> > If you're using 1.3.24 try reverting to 1.3.22 (which I know works) and
> > see if that fixes it.
>
> 1.3.24 is broken in more than one way; I am using the latest CVS version
> without problems.
>
> Balazs
>
>
>
>
