Fetch: X-Requested-With request header is not set with XMLHttpRequest

Created on 19 Oct 2014 · 4Comments · Source: github/fetch

Some back-ends check on X-Requested-With header to see if it is an ajax request. With fetch, that header isn't set.

Source

hannesvdvreken

Most helpful comment

The XMLHttpRequest used by the fetch polyfill is an implementation detail. When browsers start shipping window.fetch natively, the X-Requested-With header won't be sent along with the request. So it would be an error to rely on that header being sent from the polyfill.

Here's a simple fetch wrapper we're using at GitHub that provides some of the missing behavior from Rails' integration with jQuery.

https://gist.github.com/dgraham/92e4c45da3707a3fe789

In practice, sites are going to need a small wrapper like this to work with window.fetch as easily as jQuery's $.ajax.

/cc @annevk This wrapper might or might not inform the fetch spec.

dgraham on 19 Oct 2014

👍2

All 4 comments

X-Requested-With is just a header convention, its not part of any XHR or the Fetch spec.

josh on 19 Oct 2014

👍1

Here's a simple fetch wrapper we're using at GitHub that provides some of the missing behavior from Rails' integration with jQuery.

https://gist.github.com/dgraham/92e4c45da3707a3fe789

In practice, sites are going to need a small wrapper like this to work with window.fetch as easily as jQuery's $.ajax.

/cc @annevk This wrapper might or might not inform the fetch spec.

dgraham on 19 Oct 2014

👍2

:+1: Thanks for the information!

hannesvdvreken on 19 Oct 2014

@dgraham that wrapper seems to assume a document environment. The CSRF stuff would break in a worker environment.

@dgraham if you want standardized CSRF tokens, perhaps email [email protected] or [email protected] (need to subscribe first for the former). Might be worth doing.