Hello guys, Do you mind if I chime in? I agree that verify should not use 400 HTTP status code to indicate failure of verifying variable values. I don't think that even an failure to parse HTTP request body should be indicated in such a way as long as there were no failure on HTTP protocol level. Beside, forcing browser to show its standard error page for 400 error code when user simply made a mistake entering e- mail address or phone number is the straightest way to scare your users to death.
> HTTP is an application protocol (which resides on top of the stack), IMHO, you are mixing HTTP being an application layer protocol in OSI model with Pylons/WSGI application protocol that is unique to particular application and is partially defined by application form validation rules that are not part of HTTP protocol. Cheers, Alex --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
