|
||||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||||
|
||||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||||
Pushed upstream https://github.com/jboss-jdf/ticket-monster/commit/d6824a0e3a0dd367137a846aecd920871d994ead
This required a server-side change to return HTTP 204 No Content responses instead of HTTP 200 OK. This is primarily due to a change in jQuery 1.9 that treats empty 200 OK responses as errors which cascaded to Backbone and eventually resulted in no updates to the view.
The server-side change now results in a 204 response preventing this hidden failure.