>As for what you said, if I would send two headers, that means the current transaction will be shown as is. However, all other transactions should be ok as the header is reset at each transaction.

I don't think it's a problem of headers getting saved from transaction to transaction, because everyone gets their own cookie information, and not somebody else's. From the garbage I've seen, it looks like just the cookies are being displayed right? You are building your cookies and then calling Redirect. Redirect _should_ clear out the cookie data (it calls Response::Clear), but perhaps for some reason the output is not getting cleared before the redirect header is inserted. I suppose this would explain the output we get. You might try calling Response.Clear yourself before calling the Redirect method, or to be really brute, set Response.cOutput to nothing manually just to see if that makes a difference.

What's so annoying about this is that it occurs seemingly randomly, and so might be _very_ difficult to trace down...