230035 - Mozilla does not support the Content-Location header (RFC2616)

Status: VERIFIED DUPLICATE of bug 109553

(Core :: Networking: HTTP, defect)

Description

[Marek Stępień [:marcoos, inactive]]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031206 Firebird/0.7+ (marcoos/pentium3+sse2+mmx)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031206 Firebird/0.7+

The Content-Location header should influence the way the browser translates
relative filenames into full URLs.

E.g. if a page at http://someserver/foo.html has that header set to
"http://someserver/somewhere/else/bar.html", and if a user clicks on a link to
"foobar.html" in foo.html, the http://someserver/somewhere/else/foobar.html page
should be loaded, not http://someserver/foobar.html.


Reproducible: Always

Steps to Reproduce:
1. Go to http://jigsaw.w3.org/HTTP/CL/
2. Click on the link saying "this link" 

Actual Results:  
Mozilla opens http://jigsaw.w3.org/HTTP/CL/ok.html 


Expected Results:  
The http://jigsaw.w3.org/HTTP/CL/far/away/ok.html should be loaded,
since the Content-Location header is
"http://jigsaw.w3.org/HTTP/CL/far/away/ContentLocation.html".


More information on Content-Location can be read at
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.14

I reproduced this bug on Linux (Moz 1.6b, 1.4 and Firebird, also Netscape 7.1),
other people reported to me that this happens on other platforms, too.

Comment 1

[Boris Zbarsky [:bzbarsky]]

*** This bug has been marked as a duplicate of 109553 ***

Comment 2

[Marek Stępień [:marcoos, inactive]]

V.