Yes, HTTP-Only cookies would be fine for this functionality. They will still be provided with the XmlHttpRequest’s request to the server. In the case of Stack Overflow, the cookies are automatically provided as part of the XmlHttpRequest request. I don’t know the implementation details of the Stack Overflow authentication provider, but that cookie data is … Read more
I know this is an old thread but I thought I would chime in. Chrome currently has a solution built in. Use CTRL+SHIFT+I (or navigate to Current Page Control > Developer > Developer Tools. In the newer versions of Chrome, click the Wrench icon > Tools > Developer Tools.) to enable the Developer Tools. From … Read more
WebSockets isn’t intended to replace AJAX and is not strictly even a replacement for Comet/long-poll (although there are many cases where this makes sense). The purpose of WebSockets is to provide a low-latency, bi-directional, full-duplex and long-running connection between a browser and server. WebSockets opens up new application domains to browser applications that were not … Read more
The jquery ajax method returns a XMLHttpRequest object. You can use this object to cancel the request. The XMLHttpRequest has a abort method, which cancels the request, but if the request has already been sent to the server then the server will process the request even if we abort the request but the client will … Read more
ko.applyBindings accepts a second parameter that is a DOM element to use as the root. This would let you do something like: <div id=”one”> <input data-bind=”value: name” /> </div> <div id=”two”> <input data-bind=”value: name” /> </div> <script type=”text/javascript”> var viewModelA = { name: ko.observable(“Bob”) }; var viewModelB = { name: ko.observable(“Ted”) }; ko.applyBindings(viewModelA, document.getElementById(“one”)); ko.applyBindings(viewModelB, … Read more
To see a tree view in recent versions of Chrome: Navigate to Developer Tools > Network > the given response > Preview
I see the status field on the jqXhr object, here is a fiddle with it working: http://jsfiddle.net/magicaj/55HQq/3/ $.ajax({ //… success: function(data, textStatus, xhr) { console.log(xhr.status); }, complete: function(xhr, textStatus) { console.log(xhr.status); } });
According to the w3 spec section 4.6.3 for XMLHttpRequest a user agent should honor the Set-Cookie header. So the answer is yes you should be able to. Quotation: If the user agent supports HTTP State Management it should persist, discard and send cookies (as received in the Set-Cookie response header, and sent in the Cookie … Read more
success has been the traditional name of the success callback in jQuery, defined as an option in the ajax call. However, since the implementation of $.Deferreds and more sophisticated callbacks, done is the preferred way to implement success callbacks, as it can be called on any deferred. For example, success: $.ajax({ url: “https://stackoverflow.com/”, success: function(data) … Read more
The reason for the error is the same origin policy. It only allows you to do XMLHTTPRequests to your own domain. See if you can use a JSONP callback instead: $.getJSON( ‘http://<url>/api.php?callback=?’, function ( data ) { alert ( data ); } );