>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?
Erik Moore
Clientelligence