disable debug mode, enable remote custom errors, and disable trace in one declaration

by Euo 3. August 2008 01:52

For security purposes, we should not put websites into  production environment with debug mode enabled nor trace enabled. I got this tip from a book published by SAMS. On the production server, add the following element inside the system.web section of the machine.config file:


<deployment retail=“true”/>

Adding this element disables debug mode, enables remote custom errors, and disables tracing on all of the ASP.NET websites on that server. 

Tags:

Development

About the author

Something about the author

Month List

Page List