Permalink
Browse files

Changed mentions of CMS to Django in django.core xheaders and exceptions

git-svn-id: http://code.djangoproject.com/svn/django/trunk@55 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent eb9c9ab commit a051772b85624632771c65b41ad42df452978d94 @adrianholovaty adrianholovaty committed Jul 15, 2005
Showing with 5 additions and 5 deletions.
  1. +2 −2 django/core/exceptions.py
  2. +3 −3 django/core/xheaders.py
@@ -1,4 +1,4 @@
-"Global CMS exceptions"
+"Global Django exceptions"
from django.core.template import SilentVariableFailure
@@ -23,4 +23,4 @@ class ViewDoesNotExist(Exception):
class MiddlewareNotUsed(Exception):
"This middleware is not used in this server configuration"
- pass
+ pass
@@ -1,10 +1,10 @@
"""
-Some pages in our CMS are served up with custom HTTP headers containing useful
-information about those pages -- namely, the contenttype and object ID.
+Pages in Django can are served up with custom HTTP headers containing useful
+information about those pages -- namely, the content type and object ID.
This module contains utility functions for retrieving and doing interesting
things with these special "X-Headers" (so called because the HTTP spec demands
-that custom headers are prefxed with "X-".)
+that custom headers are prefxed with "X-").
Next time you're at slashdot.org, watch out for X-Fry and X-Bender. :)
"""

0 comments on commit a051772

Please sign in to comment.