> >>I don't understand, 400 is a common way to say that the request was
> >>wrong, do you want something else?
> >
> > On firefox, a 400 triggers the
> >
> > error: function(xhr, textStatus, errorThrown) {..}
> >
> > so only displays 'Network or server error!' rather than the validation
> > respons
2017-02-16 9:08 GMT+01:00 Greg Huber :
>>I don't understand, 400 is a common way to say that the request was
>>wrong, do you want something else?
>
> On firefox, a 400 triggers the
>
> error: function(xhr, textStatus, errorThrown) {..}
>
> so only displays 'Network or server error!' rather than the
>I don't understand, 400 is a common way to say that the request was
>wrong, do you want something else?
On firefox, a 400 triggers the
error: function(xhr, textStatus, errorThrown) {..}
so only displays 'Network or server error!' rather than the validation
response.
Maybe a 400 on other browse
2017-02-13 11:06 GMT+01:00 Greg Huber :
> Was looking at some client side validation, with the showcase app. I use
> firefox and it was not working, it just returned Network or server error!
>
> https://struts.apache.org/docs/ajax-validation.html
>
> The ajax call was returning 400, so falls back o
Was looking at some client side validation, with the showcase app. I use
firefox and it was not working, it just returned Network or server error!
https://struts.apache.org/docs/ajax-validation.html
The ajax call was returning 400, so falls back onto the error function and
just displays the netwo
