Using jQuery v3+, Q($.ajax) promise returned doesn't seem to resolve

[ericnewton76]

https://stage-cremationbasics.cp-access.com/ un:arbormemorialreview pw:Arb0rMem0rial!

• Hit "Get Pricing Now", button is towards bottom of page.
• Hit any of the 3 selects, near bottom of page
• Hit "Continue to Step 2"
• Scroll down, Hit "Continue to Step 3"
• Scroll down, Hit "Continue to Step 4"
• Scroll down, Hit "Continue to Step 5"
• On "Build and Price" heading page, click "I'm ready to make arrangements now..."
• Open chrome developer tools, sources, assets/scripts/pricing-bundle.js
• place breakpoints on line 8153,8154
• go back to fill in form, add "TESTING" anywhere in Comments or Notes please
• hit Submit.

Expected behavior: breakpoint on 8154 is hit after Q($.ajax({})) resolves. Note that if you actually hit 8154, the following lines will probably fail, I've never been able to get to that point. jquery ajax is resolving its promise as valid, but its not coming back through then().

Actual behavior: then() never resolves with valid data.

If you run things through Fiddler, the service call to WCOService.asmx/ShopifyCall is return 200 OK, but somewhere between jquery ajax and Q, its resolving as rejected. Of note, Jquery Ajax documentation notates that the promise behavior changes in v3 compared to prior...

on http://api.jquery.com/jquery.ajax/ search for "deprecation notice", although i'm not sure this is the real issue.

[ericnewton76]

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.

[ericnewton76]

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