I am surprised that HEAD requests follow the redirects and I would expect to get the HEAD results back and read the information out.
Me too, I'll write in a patch for that - Damn, it'll create conflicts with all my other HTTP patches from this evening :)
As for returning the redirected url - which of the many urls would you return?
The last one. However, You're right i think, Its not really a typical use-case.. It'd be a pretty rare occurance.
Lets skip returning the URL, and stick to preventing redirects for Head requests.
