Using jQuery v3+, Q($.ajax) promise returned doesn't seem to resolve about q HOT 2 CLOSED

I think I just stumbled onto what the problem is.

XmlHttpRequest, in all its (idiotic) wisdom, will silently follow a Location header and jquery ajax bubbles that out as a rejection. However, this is standard practice for REST apis on POST to respond with 201 Created and a Location header of where to go to retrieve the newly POST'd data.

Therefore the jquery ajax is detecting the XmlHTtpRequest redirect, and for some reason beyond logic, raises its own reject which bubbles out to Q's reject. Here's the crazy part... the old success callback is called before calling the reject on the returned jquery promise!

Aye vay.

from q.

Actually it was stupid ASMX WebMethod plopping {"d":null} at the end of a long response grrrrrrrrrrrrrrrrrrrrrrrr

from q.