You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it's bad that users can raise exceptions in the application by submitting unexpected data, e.g. by submitting a string when an array of a compound form is expected. So they can manually force a page to return http code "500 Internal Server Error" at any time. It's of course not a security issue as only the hacker himself sees the error. But IMO it's bad design because it is not fault-tolerant. And it's also quite wrong that users can externally raise internal errors. Furthermore they can spam the log entries this way.
The text was updated successfully, but these errors were encountered:
the Form component is not aware of the way you handle your error reporting. So it cannot send a 4xx response for you (it does not send a 5xx for you either, or any other response).
However, all exceptions coming from the form component extend FormException, so you can handle them the way you want.
I think it's bad that users can raise exceptions in the application by submitting unexpected data, e.g. by submitting a string when an array of a compound form is expected. So they can manually force a page to return http code "500 Internal Server Error" at any time. It's of course not a security issue as only the hacker himself sees the error. But IMO it's bad design because it is not fault-tolerant. And it's also quite wrong that users can externally raise internal errors. Furthermore they can spam the log entries this way.
The text was updated successfully, but these errors were encountered: