We have a bunch of websites/applications with debug="true" in their web.config files.
We want to override this at a server level with retail="true", as described here
However, these sites still respond to the http DEBUG verb with a 200, which is at least one difference.
I would like to know if this is the only one or if there are other (perhaps more insecure) implications of relying on retail="true"
There is some similar question here, but no clear answer to the question I am asking.
Slide deployment in retail is a strategy used by retailers to increase sales by making it easier for customers to find and purchase products. This can be done by deploying slides throughout the store that highlight products and make them more visible to customers.
Debugging is enabled when the debug attribute in the compilation element is set to true. If the debug attribute is true, change the debug attribute to false. The following code sample shows the compilation element with debug set to false: XML Copy.
Retail mode definitely disables debug mode. It also turns off tracing and sets custom errors on - are you seeing this? Have you had a reboot? How are you issuing the debug request?
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With