Skip to main content

Bug Tracker

Side navigation

#12738 closed bug (invalid)

Opened October 15, 2012 09:10PM UTC

Closed October 31, 2012 08:57AM UTC

422 Status Code Issue?

Reported by: danilo.dev@gmail.com Owned by: danilo.dev@gmail.com
Priority: undecided Milestone: None
Component: unfiled Version: 1.7.1
Keywords: Cc:
Blocked by: Blocking:
Description

I'm working with backbone, an it uses jquery for save (jQuery.ajax).

When I tried to save an invalid form, rails returns the 422 Status Code (this is correct), but in my javascript ajax petition, jQuery executes the success callback, when it should excecute error.

Am I wrong?

Anyway, I solved this problem using the statusCode parameter, and get the code error there. I'm only informing.

I'm asking here, because a similar question was done in Backbone issues https://github.com/documentcloud/backbone/issues/1249, but is very old.

I looked here if the question was done, but I didn't find it.

Attachments (0)
Change History (3)

Changed October 15, 2012 09:24PM UTC by danilo.dev@gmail.com comment:1

I'm doing some test, and I can see that jquery is taking 422 as an error when the used method is POST, but is not when is PUT.

Changed October 16, 2012 04:13PM UTC by elgreg comment:2

owner: → danilo.dev@gmail.com
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket.

Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, use this boilerplate: http://jsfiddle.net/FrKyN/. Open the link and click to "Fork" (in the top menu) to get started.

Changed October 31, 2012 08:57AM UTC by trac-o-bot comment:3

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!