Removed X-Requested-With to stop cross domain issues

[jamescorbett]

When working with Cross domain enabled services often X-Requested-With isn't added to the allowed headers and Chrome will throw an error.

I've removed the offending line but I don't know why it was added in the first place.

[jimhigson]

Hi, yes, good point.

There's a fairly good convention where AJAX libraries add this header. I'm not sure how important it is though - in all honesty, in all my days doing web applications I've never actually relied on it for anything.

My usual approach is to look what jQuery does for issues like this. They only set the header for same-domain requests - see here - following the principle of least surprise that sounds pretty sensible.

I'll have a bit of time on a train pretty soon. I'll take a look at copying jQ and retag a new minor version.

[jimhigson]

Fixed as of v.1.14.5 so that this header is only added if the request is not cross-origin.

[jamescorbett]

Thank you, I can switch back to the vanilla library now :)