Thanks for testing this!

I do need a solution that sends only one Set-Cookie header.

Ian

On Fri, Aug 14, 2009 at 6:15 AM, Nick Pearson wrote:

> In my tests, it actually adds a second Set-Cookie header unfortunately
> (I'm using nginx 0.8.7). In my limited testing, Firefox 3.5
> recognizes both Set-Cookie headers (and stores the cookie(s) in each),
> but Safari 3.2.3 seems to only recognize the first of the Set-Cookie
> headers.
>
> Does anyone know if there's support for a change_header directive
> through a module, or are we limited to add_header?
>
> Nick
>
>
> On Fri, Aug 14, 2009 at 12:08 AM, Ian Shafer wrote:
> > Thank you so much for your solution. I'll test this tomorrow. Will the
> > proposed solution send two Set-Cookie headers? Or does the add_header
> > directive replace the first Set-Cookie header?
> >
> > Ian
> >
> > On Thu, Aug 13, 2009 at 5:10 PM, Marcus Clyne
> wrote:
> >>
> >> Hi,
> >>
> >> Nick Pearson wrote:
> >>>
> >>> Oops, I messed up on the add_header line. It should have been:
> >>>
> >>> add_header Cookie "something=$cookie_something your_suffix_here";
> >>>
> >>
> >> Should be
> >>
> >> add_header Set-Cookie "something=$cookie_something your_suffix_here";
> >>
> >>
> >> Cheers,
> >>
> >> Marcus.
> >>
> >
> >
>
>