Changeset 7702
- Timestamp:
- 06/19/08 07:13:43 (5 months ago)
- Files:
-
- django/trunk/docs/settings.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/settings.txt
r7676 r7702 389 389 Still, note that there are always going to be sections of your debug output that 390 390 are inappropriate for public consumption. File paths, configuration options, and 391 the like all give attackers extra information about your server. Never deploy a 392 site with ``DEBUG`` turned on. 391 the like all give attackers extra information about your server. 392 393 It is also important to remember that when running with ``DEBUG`` turned on, Django 394 will remember every SQL query it executes. This is useful when you are debugging, 395 but on a production server, it will rapidly consume memory. 396 397 Never deploy a site into production with ``DEBUG`` turned on. 393 398 394 399 DEBUG_PROPAGATE_EXCEPTIONS
