Forcing a 500 error (IIS6)
- February 27th, 2011
- Write comment
I was looking through the IIS settings of a server running Server 2003 (or 2008) and noticed “Show friendly error messages” was enabled. The setting is pretty self explanatory and should probably be disabled on a production server, but what do “unfriendly” error messages look like? Is it standard practice to test server error pages – other than 404 pages, which are easy to test. If so, is accessing the (presumably) static html file directly sufficient?
I tend to err on the side of caution and wanted to see an actual error in action. Fortunately, IIS makes this pretty easy. If you have a form, enter a ‘tag’ in a field and submit the form. Something like `<script>` ought to do it.
tl;dr: Submit a form with a tag (eg `<script>`) in one of the fields.
