I am implementing abortable fetch calls.

There are basically two reasons for aborting the fetch on my page:

• the user decides he/she does not want to wait for the AJAX data anymore and clicks a button; in this case the UI shows a message "call /whatever interrupted"
• the user has moved to another part of the page and the data being fetched are no longer needed; in this case I don't want the UI to show anything, as it'd just confuse the user

In order to discriminate the two cases I was planning to use the reason parameter of the AbortController.abort method, but the .catch clause in my fetch call always receives a DOMException('The user aborted a request', ABORT_ERROR).

I have tried to provide a different DOMException as reason for the abort in case 2, but the difference is lost.

Has anyone found how to send information to the fetch .catch clause with regards to the reason to abort?

I am implementing abortable fetch calls.

There are basically two reasons for aborting the fetch on my page:

• the user decides he/she does not want to wait for the AJAX data anymore and clicks a button; in this case the UI shows a message "call /whatever interrupted"
• the user has moved to another part of the page and the data being fetched are no longer needed; in this case I don't want the UI to show anything, as it'd just confuse the user

In order to discriminate the two cases I was planning to use the reason parameter of the AbortController.abort method, but the .catch clause in my fetch call always receives a DOMException('The user aborted a request', ABORT_ERROR).

I have tried to provide a different DOMException as reason for the abort in case 2, but the difference is lost.

Has anyone found how to send information to the fetch .catch clause with regards to the reason to abort?

• javascript
• google-chrome
• fetch-api
• domexception
• abortcontroller

2 Answers 2

In the example below, I demonstrate how to determine the reason for an abortion of a fetch request. I provide inline ments for explanation. Feel free to ment if anything is unclear.

Re-run the code snippet to see a (potentially different) random result

'use strict';

function delay (ms, value) {
  return new Promise(res => setTimeout(() => res(value), ms));
}

function getRandomInt (min = 0, max = 1) {
  return Math.floor(Math.random() * (max - min + 1)) + min;
}

// Forward the AbortSignal to fetch:
// https://docs.github./en/rest/repos/repos#list-public-repositories
function fetchPublicGHRepos (signal) {
  const headers = new Headers([['accept', 'application/vnd.github+json']]);
  return fetch('https://api.github./repositories', {headers, signal});
}

function example () {
  const ac = new AbortController();
  const {signal} = ac;

  const abortWithReason = (reason) => delay(getRandomInt(1, 5))
    .then(() => {
      console.log(`Aborting ${signal.aborted ? 'again ' : ''}(reason: ${reason})`);
      ac.abort(reason);
    });

  // Unless GitHub invests HEAVILY into our internet infrastructure,
  // one of these promises will resolve before the fetch request
  abortWithReason('Reason A');
  abortWithReason('Reason B');

  fetchPublicGHRepos(signal)
    .then(res => console.log(`Fetch succeeded with status: ${res.status}`))
    .catch(ex => {
      // This is how you can determine if the exception was due to abortion
      if (signal.aborted) {
        // This is set by the promise which resolved first
        // and caused the fetch to abort
        const {reason} = signal;
        // Use it to guide your logic...
        console.log(`Fetch aborted with reason: ${reason}`);
      }
      else console.log(`Fetch failed with exception: ${ex}`);
    });

  delay(10).then(() => console.log(`Signal reason: ${signal.reason}`));
}

example();

The abort reason is available in the signal through the reason property. If you set the signal yourself, that's easy to access.

https://developer.mozilla/en-US/docs/Web/API/AbortSignal

So when fetch throws an error, if it is a DOMException with an 'AbortError' name, you may rely on the signal's reason. Note that the aborted property of the signal might not reliable depending on where you check it because the signal could be triggered after fetch threw another kind of exception.

const controller = new AbortController();
setTimeout(() => controller.abort('Timeout'), 30000);
try {
  const response = await fetch('some_url', { signal: controller.signal });
  console.log('Fetch response:', response);
} catch (error) {
    if (error instanceof DOMException && error.name === 'AbortError') {
      console.warn('Fetch aborted:', signal.reason);
    } else {
      console.error('Fetch error:', error);
    }
  }
}

You may also make your own fetch function to get the proper exception:

async function customFetch(url, params) {
  try {
    return fetch(url, params);
  } catch (error) {
    if (error instanceof DOMException && error.name === 'AbortError') {
      // Either we have an AbortError and the signal throws...
      params?.signal?.throwIfAborted();
    }
    // Or rethrow exception as is
    throw error;
  }
}

By using this custom function, the exception made on abort by the fetch function is replaced by the AbortSignal exception:

const controller = new AbortController();
setTimeout(() => controller.abort('Timeout'), 30000);
try {
  const response = await customFetch('some_url', { signal: controller.signal });
  console.log('Fetch response:', response);
} catch (error) {
    // Now when the request is aborted, the reason is thrown as a plain string
    if (error === 'Timeout') {
      console.warn('Fetch timeout');
    } else {
      console.error('Fetch error:', error);
    }
  }
}

Note that calling the signal's throwIfAborted in the customFetch function ensures that the exception thrown is standard (the abort reason as provided), but you may throw your own exception instead.