On 15-7-2012 21:30, Jani Tiainen wrote: > In case of incorrect request I prefer to raise 400 (Bad Request) with some > explanation what went wrong. Since 500 is usually meant for "catch all" > unexpected errors that happened in web server and server can't be more > precise what happened. I've done that according to RFC 2616 (HTTP 1.1 > Specification) where is said that 4xx codes are meant for "client side > error" (Section 10.4), and 5xx which means "server error" (Section 10.5)
Yeah, this is one of the harder ones. Is it still a client error if she clicks a server generated link? ;) -- Melvyn Sopacua -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
