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
This commit is contained in:
parent
eb9c9ab4d0
commit
a051772b85
|
@ -1,4 +1,4 @@
|
||||||
"Global CMS exceptions"
|
"Global Django exceptions"
|
||||||
|
|
||||||
from django.core.template import SilentVariableFailure
|
from django.core.template import SilentVariableFailure
|
||||||
|
|
||||||
|
@ -23,4 +23,4 @@ class ViewDoesNotExist(Exception):
|
||||||
|
|
||||||
class MiddlewareNotUsed(Exception):
|
class MiddlewareNotUsed(Exception):
|
||||||
"This middleware is not used in this server configuration"
|
"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
|
Pages in Django can are served up with custom HTTP headers containing useful
|
||||||
information about those pages -- namely, the contenttype and object ID.
|
information about those pages -- namely, the content type and object ID.
|
||||||
|
|
||||||
This module contains utility functions for retrieving and doing interesting
|
This module contains utility functions for retrieving and doing interesting
|
||||||
things with these special "X-Headers" (so called because the HTTP spec demands
|
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. :)
|
Next time you're at slashdot.org, watch out for X-Fry and X-Bender. :)
|
||||||
"""
|
"""
|
||||||
|
|
Loading…
Reference in New Issue