[
https://issues.apache.org/jira/browse/WW-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897443#comment-15897443
]
Lukasz Lenart commented on WW-4750:
-----------------------------------
There is no rule to return "400" but it's a good practice, please see
http://stackoverflow.com/questions/3290182/rest-http-status-codes-for-failed-validation-or-invalid-duplicate
http://stackoverflow.com/questions/8944168/restful-service-how-to-respond-if-validation-failed
The error is thrown in jQuery because you are missing JavaScript {{.error()}}
handler to handle errors from server side. Also as I already posted you can
revert to previous behaviour with this:
{code:xml}
<interceptor-ref name="jsonValidation">
<param name="validationFailedStatus">200</param>
</interceptor-ref>
{code}
> Why JSONValidationInterceptor return Status Code 400 BAD_REQUEST instead of
> 200 SUCCESS
> ---------------------------------------------------------------------------------------
>
> Key: WW-4750
> URL: https://issues.apache.org/jira/browse/WW-4750
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - JSON
> Affects Versions: 2.5.10
> Environment: Jdk 1.7, Windows 10, jQuery 1.7.2
> Reporter: COMBEAU
> Priority: Minor
> Labels: docuentation, json, validation
> Fix For: 2.5.next
>
> Attachments: Issue in jQuery 1.7.2.png
>
>
> Since I have made the upgrade of my Struts 2.5.8 to 2.5.10, all my POST Ajax
> call via jQuery with the parameter "struts.enableJSONValidation=true" return
> status code 400 Bad Request when my validation on server side is wrong.
> And I have an issue in the caller jQuery.
> {quote}
> Failed to load resource: the server responded with a status of 400 (Bad
> Request)
> {quote}
> Before in 2.5.8 and all previous versions the status code was 200.
> What is the reason of this changes because jQuery doesn't understand this and
> it's problematic. I see this
> [WW-4728|https://issues.apache.org/jira/browse/WW-4728] but in this bug it
> was not mention that the status code has to be changed.
> Please provide example in the documentation if the reason of the change is a
> specific reason
> Thank you in advance for your help.
> Best regards,
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
