struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 29848] - Return appropriate status code when form validation fails
Date Mon, 04 Jul 2005 13:44:10 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29848>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29848





------- Additional Comments From jain@gmx.net  2005-07-04 15:44 -------
Strictly speaking you are right, a validation error is not a syntax error, but I
don't think that such a narrow definition is the intent of the specification.
More likely in my opinion is that 400 is ment to be similar to 500, except for
user rather than server errors.

In any case, my point is that returning 200 even though there was an error
doesn't seem like a very good practice. If you are accessing the web interface
programmatically (think REST), you won't know that your input was invalid until
your parser crashes - if you are lucky.

Come to think of it, I bet you can find plenty of pages that contain nothing but
an error message, but were happily indexed by Google (which does not yet
understand English very well :-)

Of course I can work around this, as Don Brown suggests, but I think it would be
great if the framework returned appropriate status codes by default, as few
people have time to care about such issues.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message