Setting up redirect in web.config file

by

  1. Open web.config in the directory where the old pages reside

  2. Then add code for the old location path and new destination as follows:

     <configuration>
   <location path="services.htm">
     <system.webServer>
       <httpRedirect enabled="true" destination="http://example.com/services" httpResponseStatus="Permanent" />
     </system.webServer>
   </location>
   <location path="products.htm">
     <system.webServer>
       <httpRedirect enabled="true" destination="http://example.com/products" httpResponseStatus="Permanent" />
     </system.webServer>
   </location>
 </configuration>

You may add as many location paths as necessary.

More Related Contents:

  1. Using different Web.config in development and production environment
  2. Meaning
  3. Access-control-allow-origin with multiple domains
  4. Forms authentication timeout vs sessionState timeout
  5. Avoid web.config inheritance in child web application using inheritInChildApplications
  6. How to increase request timeout in IIS?
  7. Which gets priority, maxRequestLength or maxAllowedContentLength?
  8. Setting up connection string in ASP.NET to SQL SERVER
  9. Use Visual Studio web.config transform for debugging [duplicate]
  10. How to set the Default Page in ASP.NET?
  11. ASP.NET web.config: configSource vs. file attributes
  12. Difference between and ?
  13. IIS URL Rewrite and Web.config
  14. Reading web.config from JavaScript
  15. Web Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
  16. How to configure invariant culture in ASP.NET globalization?
  17. Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’
  18. Nested ASP.NET ‘application’ within IIS inheriting parent config values?
  19. Store String Array In appSettings?
  20. How to encrypt one entry in web.config
  21. Is it possible to configure a location in Web.config to only allow local connections
  22. Allow anonymous authentication for a single folder in web.config?
  23. Programmatically register HttpModules at runtime
  24. The configuration section ‘system.web.extensions’ cannot be read because it is missing a section declaration
  25. web.config and app.config confusion
  26. Unrecognized attribute ‘targetFramework’. Note that attribute names are case-sensitive
  27. Specify more than one directory in Web.Config’s Location Path element
  28. Editing Web.config programmatically
  29. How can I reference an appSetting in a different part of web.config
  30. URL Routing, Image Handler & “A potentially dangerous Request.Path value”

Leave a Comment