summaryrefslogtreecommitdiff
path: root/django
diff options
context:
space:
mode:
authorBrandon Adams <emidln@gmail.com>2012-11-12 17:17:05 -0500
committerBrandon Adams <emidln@gmail.com>2012-11-16 10:19:54 -0500
commitd8ee46afff913975404887cdd2eec635a03013f8 (patch)
treec1a35c4383c50ea0e68d05b7bd5a3a09a3421e11 /django
parentff0d3126afbc30ae1aab3a9d352300e59937fe5e (diff)
comment_will_be_sent can cause a 400, not a 403
Doc cleanup for django.contrib.comments.signals.comment_will_be_sent If a receiver returns False, an HttpResponse with status code 400 is returned. A test case already exists confirming this behavior. Updated docs to reflect reality.
Diffstat (limited to 'django')
-rw-r--r--django/contrib/comments/signals.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/django/contrib/comments/signals.py b/django/contrib/comments/signals.py
index fe1083bd14..079afaf03a 100644
--- a/django/contrib/comments/signals.py
+++ b/django/contrib/comments/signals.py
@@ -6,7 +6,7 @@ from django.dispatch import Signal
# Sent just before a comment will be posted (after it's been approved and
# moderated; this can be used to modify the comment (in place) with posting
# details or other such actions. If any receiver returns False the comment will be
-# discarded and a 403 (not allowed) response. This signal is sent at more or less
+# discarded and a 400 response. This signal is sent at more or less
# the same time (just before, actually) as the Comment object's pre-save signal,
# except that the HTTP request is sent along with this signal.
comment_will_be_posted = Signal(providing_args=["comment", "request"])