[
https://issues.apache.org/struts/browse/STR-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41342
]
Paul Benedict commented on STR-2119:
------------------------------------
It's almost worth considering. In my Struts applications, if I have to retrieve
data through GET, my validation errors go to a 404 page. I consider invalid GET
input to be equal to a Resource Not Found (404). Only if I am actually
collecting user input (POST), will I use a standard input error page.
I am willing to consider the idea that a validation error on a GET can trigger
a 404 error. The 404 error can either be added to the CRP or as an internal
action.
> Return appropriate status code when form validation fails
> ---------------------------------------------------------
>
> Key: STR-2119
> URL: https://issues.apache.org/struts/browse/STR-2119
> Project: Struts 1
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1 Final
> Environment: Operating System: other
> Platform: Other
> Reporter: Eric Jain
> Assignee: Struts Developers
> Priority: Minor
>
> When redisplaying a form after validation has indicated a failure, a status
> code
> such as "400 Bad Request" should be used in place of "200 OK". This simplifies
> testing, and is important for applications that need to interact with the web
> interface of an application directly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
