Sok Ann Yap wrote: > Currently, the validate decorator always return 200 OK when validation > fails. I think 400 Bad Request is more appropriate here, so that it > will be easier for non-browser application to interact with the pylons > app. Maybe we can add a parameter to @validate that is defaulted to > 200, to make it backward compatible.
Well, the thread is old and kind of closed, but just for the record I think a 400 Bad Request code is entirely reasonable for this case, and a good use of that response code, with little ill effect (assuming, as was noted, that you respond with a large enough body to avoid the IE error page). -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
