> From: Markus Reis [mailto:[EMAIL PROTECTED]
> Subject: Re: RE: multiple Set-Cookie headers in initial http response
>
> I have the impression that this happens already before the
> webapp comes into play, because the HttpSessionListener
> implementation prints out thos
> Sounds like something in the webapp is invalidating the current session
> and creating a new one each time it processes a parameter. Perhaps code that
> should be executed once is incorrectly placed inside a loop?
I have the impression that this happens already before the webapp comes into
pla
