[
https://issues.apache.org/struts/browse/STR-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41443
]
Hugh Winkler commented on STR-2119:
-----------------------------------
It's GREAT to see this raised as an issue. It's entirely worth pursuing. Eric's
spot on: web apps need to return 4XX (almost certainly 400 for POST; 404 is
right for GET) on validation errors, to comply with webarch.
A practical consideration is getting the browser to display the returned entity
-- which would be the same page you generate now. Last I checked, IE 6 and
earlier used to display its own error page for 4xx, *unless* the returned
entity was longer than a certain length.
> 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: Paul Benedict
> 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.
