If from an ASP page you try to use Response.Redirect after having written anything to the browser, you’ll get an error saying that the page’s headers have already been written. To avoid this you should put the code that checks if the browser needs to be redirected to another page at the very beginning of the page, before any HTML code. A better approach is to turn on page buffering (which is on by default in IIS 5).

There are cases, however, when you find out you need to redirect the user to another page after sending partial output to the browser. For example, this happens if your ASP code performs a time consuming task, and you want to display a message or an animated image that shows the progress status.

How to redirect to another page if the browser has already received some html? The trick is to send to the browser a client side script that do the action. As soon as the browser receives the script, it will be processed performing the redirection. The client side script can load another page by setting the location.href property. Here’s the ASP function that you can use instead of Response.Redirect:

Sub RedirectTo(strURL)     Response.Write ""End Sub

To show a complete example, consider the following script:

<%Sub RedirectTo(byval strURL)     Response.Write "<SCRIPT LANGUAGE=""JavaScript"" TYPE=""text/javascript" _        ">" & "location.href = '" & strURL & "';" & "</SCRIPT>"End Sub Response.Write "<H1>The server is processing your order. Please " _    & "wait...</H1>"' write here the code that actually performs the time consuming task' ...' ...' at the end, redirect the browser to the confirmation pageRedirectTo "confirm.htm"%>