Is it possible for XHR HEAD requests to not follow redirects (301 302)?

There isn't, this isn't exposed behavior you can stop It's because of the spec you linked already the specified behavior is that XmlHttpRequest should transparently follow redirects...under the covers unfortunately, and not in a way you can prevent It's this way to try and make things easier, if resources move, etc...but when it was designed and the spec laid out, all these redirection services weren't out there. There just wasn't a strong need for any other behavior or ability to prevent it, I think with as many redirects hitting the web not we'll see the ability added, but who knows when every browser would support it.

There isn't, this isn't exposed behavior you can stop. It's because of the spec you linked already, the specified behavior is that XmlHttpRequest should transparently follow redirects...under the covers unfortunately, and not in a way you can prevent. It's this way to try and make things easier, if resources move, etc...but when it was designed and the spec laid out, all these redirection services weren't out there.

There just wasn't a strong need for any other behavior or ability to prevent it, I think with as many redirects hitting the web not we'll see the ability added, but who knows when every browser would support it.

The W3C specification requires that redirects are followed automatically, as @Nick suggested in the other answer. However a property to disable redirects is being considered by the W3C for a future version of this specification: This specification does not include the following features which are being considered for a future version of this specification: load event and onload attribute; error event and onerror attribute; progress event and onprogress attribute; abort event and onabort attribute; Timers have been suggested, perhaps an ontimeout attribute; Property to disable following redirects; responseXML for text/html documents; Cross-site XMLHttpRequest; responseBody to deal with byte streams; overrideMimeType to fix up MIME types; getRequestHeader() and removeRequestHeader(). However, I wouldn't hold my breath until this is implemented by all browsers.

You may want to use a server-side proxy to handle this. Simply write a short script to do a HEAD request in your favourite server-side language/framework, and then use Ajax to query this service. You would also be able to do requests to third-party domains through the proxy as a positive side-effect.

I'm mostly interested in a solution/hack for google-chrome/webkit. – antonj Sep 29 '10 at 10:50 @Blastura: Not sure about that, but I don't think it is. – Daniel Vassallo Sep 29 '10 at 10:51.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.