NS_BINDING_ABORTED Shown in Firefox with HttpFox

I am seeing some of the server calls (Used for tracking purpose) in my site getting aborted in Firefox while seeing through HttpFox. This is happening while clicking some link that loads another page in the same window. It works fine with popup. The error type shown is NS_BINDING_ABORTED. I need to know is the tracking call is hitting the server or not. It works perfectly with Internet Explorer. Is it any problem with the tool? In that case can you suggest any that can be used in Firefox too.

Because your server is not sending HTTP Expires headers, the browser is checking to see if what is in its cache is current.

The way it does this is to send the server a request saying what the date of what it has in the cache is, and the server is sending 304 status telling the client that what it has is current. In other words, the server is not sending the entire content again but instead sending just a short header to say the existing cache content is current.

What you probably need to fix, is to add Expires headers to what you are serving. Then you will see the NS_BINDING_ABORTED message change to (cache), meaning the browser is simply getting content out of its cache, knowing it has not yet expired.

I should add that, when you do a FireFox forced refresh, it assumes that you want to double-check what is in the cache, so it temporarily ignores Expires.

You shouldn't be worried just because you see something that looks like a failure code (NS_BINDING_ABORTED).

In <http://markmail.org/message/m6z77uoixf3qu7u6> a Firefox developer confirms that NS_BINDING_ABORTED is simply an indication that a page load has been stopped.

It seems perfectly normal that opening a page while another page is being loaded cancels the loads on the first page. It doesn't mean the loads were aborted before the request got sent to the server, which seems to be what you care about.

[edit: reworded & removed the bit about me not being familiar with HttpFox, as people who see this in 2022 are probably not using it anyway.]

What other javascript do you have on the page? Some javascript might be firing causing the request to be aborted.

I noticed the same thing in my application. I was redirecting the page in javascript (window.location = '/some/page.html') but then further down the block of code, I was calling 'window.reload()'. The previous redirection was aborted because window.reload was called.

I don't know what tracking you are using but it's possible that the request is being sent to your server but the request is aborted because another request was issued afterwards.

NS_BINDING_ABORTED error - Best Approach -Using a JavaScript “setInterval” method with the time delay of Min ‘0’ to max ‘100’ milliseconds based on the page load, we can execute our track link request after the default page submit request is processed.

World best solution:

var el = document.getElementById("t");
el.addEventListener("click", avoidNSError, false); //Firefox

function avoidNSError(){
  ElementInterval = setInterval(function () {
 /* Tracking or other request code goes here */
  clearInterval(ElementInterval);
 },0);

};

I have experienced a similar problem, but have identified the cause.

I have a link in the first cell of a table row, and some Javascript that replicates that link across the other TD's of the row. When I click on the 'real' link (in the first cell) I get this unwanted side-effect; when I click on other cells in the row, all is fine. I feel it's because the script is adding a second link to that first cell, when it already has one.

Hence, two instantaneous requests for the same page, with the first being aborted by the second.

This technique is fairly common, so something to look out for.

In my case, same NS_BINDING_ABORTED error, but it was because a "button" element, which I clicked to trigger an event, was missing the attribute "type" value "submit" = https://stackoverflow.com/questions/932653/how-to-prevent-buttons-from-submitting-forms

The error NS_BINDING_ABORTED can have a variety of reasons.

In my case it was garbage in the response headers received from the server, basically a HTTP protocol violation.

Using a web debugging proxy such as Fiddler may sometimes reveal such issues better than the browser's own debugging console (which today does what, I assume, HttpFox did, just better), or at least show more detailed information or clearer error messages.

I know this is a very old question but this happened to me recently with Firefox 95. The images of an ancient application made by a collegue of mine were not loaded (or loaded randomly) because of this code:

window.addEventListener('focus', function() {
   // omit other code...
   location.reload();
}

Once nested this code into a 'load' listener, the issue completely disappeared.

in my case experience, NS_BINDING_ABORTED occurred because missing closed tag between <form>...</form> example:

<form name="myform" action="submit.php" method="post">
    <div class="myclassinput">
        <input type="text" name="firstname">
        <input type="text" name="lastname">
        <input type="submit" value="Submit">

</form>

there is I am forget to write closing </div> tag before </form>.