Why not to return a custom notice without any error codes? If you still want to send a response error, I would choose from these depending on the situation, what you are implementing: 204 No Content 400 Bad Request 403 Forbidden
Aidas Bendoraitis [aka Archatas] On 9/22/06, Gábor Farkas <[EMAIL PROTECTED]> wrote: > > hi, > > imagine that you have a view function, that requires a parameter in the > querystring. > > for example, it needs to have: > > http://foo.com/bla/?param=15 > > now, what should happen if it gets: > > http://foo.com/bla/ > > ? > > in this case, technically the user should not be able to have the url > without the querystring, except if he is playing with the url :) > > i mean "what is the most standard-conformant and correct response"? > > http-404 certainly not imho. > http-500 seems also wrong, because there was no unexpected error in the > server. > > http-400 bad request maybe? > > > simply returning a http-200 with an error page seems to be the wrong > thing to do. > > > gabor > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
