Use Server.Transfer(). I don't believe the client will be sent anything other than headers using Response.Redirect() if ASP.NET buffering is enabled, but to be on the safe side use Server.Transfer(), which stops execution of the page altogether. I'll do some tests to see if data is sent when Response.Redirect() is used.[edit]The more that I think about it, Response.Redirect() should be sending a 304 response code. 304's redirect the browser to a different page. Say for instance if the page location has changed.[/edit]