Ulla Theiss wrote:
> Hello list,
>
> what is in your opinion the best zopish way to raise input validation
> errors,
> dublicate value errors, or other application errors I want to display to
> the
> user?
Use a form generation framework, or at least use the same techniques
that they do...
Ch
Hello list,
what is in your opinion the best zopish way to raise input validation
errors,
dublicate value errors, or other application errors I want to display to the
user?
Ulla
Peter Bengtsson wrote:
> Don't raise errors that cause 500 type HTTP error codes on input validation.
> It's not an e
Don't raise errors that cause 500 type HTTP error codes on input validation.
It's not an error. It's a user input error.
2009/9/7 Ulla Theiss :
> Hallo list,
>
> because the application error messages like checks of input values
> produce such error messages.
> The browser "firefox" does display t
Hallo list,
because the application error messages like checks of input values
produce such error messages.
The browser "firefox" does display these messages, but the "Internet
Explorer" with the newest updates does not.
The "Internet Explorer" displays a own error message instead. Only if
you
Ulla Theiss wrote:
> Hello list,
>
> is there a possibility to send the standard_error_message with http
> return code 200 (ok) instead of 500 (internal_server_error)?
Why would you want to? That's in violation of several http specs...
Chris
___
Zope
Hello list,
is there a possibility to send the standard_error_message with http
return code 200 (ok) instead of 500 (internal_server_error)?
Many thanks in advance,
Ulla
___
Zope maillist - Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**