| Title: | Fatals To Browser |
| URL: | http://www.rimmkaufman.com/rkgblog/2006/09/18/fatals-to-browser/ |
| Printed: | October 7, 2008 |
| Source: | The Rimm-Kaufman Group Blog, info@rimmkaufman.com |
- September 18, 2006
- 1 comment
Last night, came across this error message visiting a well-known site:
Microsoft OLE DB Provider for SQL Server error ‘80004005′
The log file for database ‘xxx’ is full. Back up the transaction log for the database to free up some log space.
/XXXX.asp, line 2208
Try as much as possible never to send internal error messages to the browser. Write them to internal logs. Such public disclosures can provide hackers helpful information to attack your site. More on web security for online retailers
If you like this post, consider subscribing to our RSS feed. You can also have new posts sent to you via email.
Possibly Similar Posts
- Security Tip: Never Display Fatal Stack Traces To Users
- Internal Blogs: Less Email, Blogging Training Wheels, Link-sharing, BizCulture
- Amazon nearly ruined my Christmas Spirit: A Lesson in Error Handling
- Protect Private Data With A Privacy Wall
- Excellent 404 Handling
Trackback
http://www.rimmkaufman.com/rkgblog/2006/09/18/fatals-to-browser/trackback/Blogs Citing This Post
- Pingback: Security Tip: Never Display Fatal Stacktraces To Users on September 19, 2008
Your Comment