Web
It is fairly common that you will need to configure a page in your web application to redirect a user to another page. The reasons for this vary, but in one specific case you may want to rethink how you are redirecting your users. When a call to Response.Redirect() is made, the server sends a response back to the client with an HTTP 302 status code, telling the client that the resource has temporarily moved and where it can find the resource. I've created a simple page, OldPage.aspx, which redirects to NewPage.aspx during the Page_Load event. Let's jump into FireBug and see exactly...