Ajax post being aborted by firefox (not seen in Chrome or IE)

Question

When using firefox, an ajax post request i have is being reported as aborted in firebug. The ajax post works fine in IE and Chrome. It is not a cross domain request. I tried looking at the issue using fiddler, and when fiddler is capturing web traffic (with options set to decrypt https) the post works. The post issue cannot be created in my local development environment, as all Firefox attempts successfully post the data I'm sending via ajax. Any idea why the post works while fiddler is running? It might give me some idea of how to get it working.

$.ajax({
            type: 'POST',
            url: '/Save',
            data: JSON.stringify(dataset),
            datatype: "html",
            contentType: "application/json",
            success: function (data, textStatus, jqXHR) {
                //alert("success");
            },
            error: function (jqXHR, textStatus, errorThrown) {
                //alert("error");
            }
        });

Also, this ajax request is called by a number of methods, and only when the largest of the datasets is sent does it fail.

How long (clock time) does the request take? Is it possible that the request is timing out? — EricLaw, Oct 31 '12 at 15:42
Is this request https? And, if you view the dataset after the stringify, is it properly formed? — Mark Schultheiss, Nov 02 '12 at 13:27
Do you issue the request from an HTTPS page? If not, probably relevant: http://stackoverflow.com/questions/1105934/ajax-using-https-on-an-http-page — CodeCaster, Nov 02 '12 at 13:37
Does it help to change the timeout? Similar to: `timeout: 4000,` or some value you like :) — Mark Schultheiss, Nov 02 '12 at 13:51
I had same problem in firefox, not sure but after making ajax call within setTimeout() function worked for me. — Abhijeet K, Jul 31 '13 at 09:03
Have you figure it out? I have exactly same issue as yours, could you tell me your solution? — Kurt Shaw, Sep 17 '13 at 13:20

score 12 · Answer 1 · edited Nov 09 '12 at 13:08

12

Try only

async: false

in ajax option, I had the same problem.

edited Nov 09 '12 at 13:08

Martijn Pieters

1,048,767
296
4,058
3,343

answered Nov 09 '12 at 12:47

Marys

139
4

score 5 · Answer 2 · answered Nov 02 '12 at 14:03

5

I would start by explicitly setting (and changing) some of the basic ajax options:

 cache: false,
 timeout: 60000,
 async: false

answered Nov 02 '12 at 14:03

no impact. problem still persists. I'm thinking firefox can't parse large json strings under https. All speculation though. – FiveTools Nov 09 '12 at 02:15
then try to reproduce the hypothesis in a isolated test-bed. – Bastl Nov 09 '12 at 12:50

Gowri · Answer 3 · 2012-11-08T19:44:43.523

What type of content your server returning. JSON or HTML content. Are you using charset=utf-8 in server content. Make sure your server response must be in JSON contentType. Another guess remove datatype: "html" from your code. Try for your luck.

If your server returns json means, try below

$.ajax({
            type: 'POST',
            url: '/Save',
            data: JSON.stringify(dataset),
            datatype: "json",
            contentType: "application/json",
            success: function (data, textStatus, jqXHR) {
                //alert("success");
            },
            error: function (jqXHR, textStatus, errorThrown) {
                //alert("error");
            }
        });

datatype: "json", contentType: "application/json" makes sense

server response is html. On the request, the data posted is json. — FiveTools, Nov 09 '12 at 02:22
@FiveTools: on your html remove charset if you have and check. — Gowri, Nov 09 '12 at 04:37

score 2 · Answer 4 · answered Nov 13 '12 at 14:17

If you send this AJAX request from an event handler (example : click of a submit button), be sure to prevent the browser's default behavior (submitting the form), until you'll have 2 HTTP requests fired, with the first being aborted.

You can use e.preventDefault() to achieve this.

I just had this trouble on IE8.

score 1 · Answer 5 · answered Nov 08 '12 at 14:54

1

Check the maximum post size setting on your server.

answered Nov 08 '12 at 14:54

Bradley Thomas

4,060
6
33
55

we are logging server exceptions, and it doesn't even get that far. We have increased the request size for posts on the server, but has no impact on resolving this issue. – FiveTools Nov 09 '12 at 02:21

score 1 · Answer 6 · answered Feb 09 '15 at 13:56

I also had similar issues and tried some of the ideas described above. I finally fixed "aborted" state by :

adding e.preventDefault(); and return false; to buttons event handlers
adding datatype: "json", contentType: "application/json", to jQuery.ajax method params.

Thx to everyone for the clues.

score 0 · Answer 7 · answered Jan 28 '15 at 17:48

This is either a cross domain issue or it is an issue with Firefox aborting your request because request is async. For cross domain you can check the origin of your request and what is allowed on webservice. You might have to read up on CORS.

If it is not cross domain then it is certainly a problem with request being async. Just change it to sync.

heez · Answer 8 · 2018-03-14T17:33:03.113

If you are using 2-way SSL auth on a CORS request, Firefox will abort your jQuery ajax requests by default. This is due to differing implementations of CORS in Firefox and Chrome. You can resolve this issue in your client code by adding withCredentials: true to your XHR instances. In jQuery, you can add this to the ajax call:

xhrFields: {
  withCredentials: true
}

Check out these bug reports for more details:

I've also noticed that Firefox still absolutely refuses to send credentials on OPTIONS preflight requests, so you will need to configure your server to not require them (which seems crazy to me in a 2-way SSL scenario).

Ajax post being aborted by firefox (not seen in Chrome or IE)

8 Answers8

Linked