Improve django.views.decorators.http docs

[Roy Smith]

require_http_methods()
require_GET()
require_POST()

None of these describe what happens if you try to access the view with the wrong method. Throw some exception? Return a 404? Cause daemons to fly out of your nose? Some additional clarity here would be useful.

[Christopher Grebs]

They return a proper 405 (Not Allowed) response. If it's really required to note this I created a small patch to mention the return value.

[anonymous]

If you are intimately familiar with HTTP, that might be obvious. I wasn't even aware the 405 code existed, so it took me a bit of experimenting to discover what it did, then some research to look up what the 405 code meant. Once I found the "Method Not Allowed" explanation, it was obvious in hind sight, but having the docs say that would have saved me a bunch of time. So, yes, I think it's "really required".

[Mathieu Agopian <mathieu.agopian@…>]

I've changed this ticket as accepted, as there's an explanation and even a doc path. Please let me know if this was to much of a bold move from me.

I've also set the "easy pickings" bit as i believe it's a pretty straightforward issue and fix.

[Roy Smith]

Thanks. But, change "This decorators will return" to "These decorators will return" :-)

[Mathieu Agopian <mathieu.agopian@…>]

fixed typo

[Mathieu Agopian <mathieu.agopian@…>]

I've attached a the documentation patch with the typo fixed. Could some please check this and remove the "patch needs improvement" if the fixed patch is ok?

[cg@…]

Replying to Mathieu Agopian <mathieu.agopian@…>:

I've attached a the documentation patch with the typo fixed. Could some please check this and remove the "patch needs improvement" if the fixed patch is ok?

Thanks for fixing the typo ;)

[Tim Graham]

In [16139]:

(The changeset message doesn't reference this ticket)

[Tim Graham]

In [16140]:

[1.3.X] Fixed #15887 - Added clarification for required_*() decorators; thanks RoySmith for the sugggestion.

Backport of r16139 from trunk.