I also understand there is some debate whether supporting Content-Location is a good idea at all (at least in web browsers). Firefox at one point started adding support, but they determined that it caused problems with broken servers (mostly IIS I believe).
As far as I, support for Content-Location was reverted because in Firefox same-document references are broken when used with some sort of base URI. I.e. if you have a document with <a href="#x"> with Content-Location: http://y/z, Firefox will go to the anchor named x in the document at http://y/z, instead of to the anchor named x in the current document.
-- Sjoerd Visscher http://w3future.com/weblog/
