>>Anyone see something wrong with this code?
>
>That code looks fine as far as I can tell. But it what you do after this that is causing the problem. For the browser to display header information, it means that your response contained two HTTP headers: the first was interpreted as the header, the second was interpreted as content. Are you calling any other framework methods after your cookie code that might be adding their own header? ExpandTemplate perhaps?

In my first reply, there is P_OUT. That should have been gcHtml. I forgot to change it when replying. P_OUT was located in the gcLocation syntax.

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. That's what I understand from the WWC logic. Isn'it? If not, then, that might be the case. Assuming, we send a second header for the same transaction, it may well be stucked in memory for all other transactions.