$.ajax using 'context' settings sets Content-Type for GET requests

Example:

$.ajaxSetup({
    statusCode: {
        401: function () {
            var $settings = this;
            var auth = $('link[rel~=authenticate]').prop('href');
            var opts = { xhrFields: { withCredentials: true } };

            $.ajax(auth, opts)
                .done(function () {
                    $.ajax($settings);
                })
                .fail(function () {
                    showErrorModalOrSomething();
                });
        }
    }
});

// This causes the statusCode handler above to trigger, which in turn
// sends the re-authentication request (which is successful) and then
// retries this same request. But when it retries this same request, 
// the Content-Type header for the GET request is set to 
// 'application-x-www-form-urlencoded' (due to the $settings object above),
// which has undesirable side effects with certain server-side frameworks

$.get(urlThatResultsIn401AtFirst, function (partial) {
    getModal().find('.modal-dialog').html(partial);
});

I would like to use this same handling across both GET and POST requests. I am open to workarounds if anyone has an idea.

[tuespetre]

@dmethvin: that is fine if it is supposed to be the default value, but please consider:

• Content-Type makes virtually no sense on a GET request
• The current implementation is inconsistent. Why would the default header not be set for the first request, but be set on the options the second time around?

[dmethvin]

Looks correct to me, the contentType is set to its default since it wasn’t specified in the original request, as mentioned in the jQuery.ajax API docs. If the server wants a different value you should set it in the options.