[Webkit-unassigned] [Bug 90967] WebKit doesn't compute relative URLs based on Content-Location

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=90967





--- Comment #6 from Brady Eidson <beidson at apple.com>  2012-11-09 13:49:11 PST ---


(In reply to comment #5)
> Just to clarify, I didn't provide the test case URL, nor do I recommend it be prioritized for fixing. I only wanted to clarify that it is a violation of the W3C spec, because there was a statement to the contrary. I agree that there's nothing to do here, but not because WebKit already adheres to the spec (it doesn't), because there's is no incompatibility with other browsers.

I actually didn't even respond to that point because it's irrelevant in this case, but since you wanted to re-iterate it...

(In reply to comment #3)
> You are right that there is no incompatibility, but I believe this is a violation of the spec as stated. The "may" is a constraint on the server, not on the client. The server may provide a Content-Location header, but if it is provided, the client "must" resolve relative URLs with respect to it.

Can you point me to precisely what passage from what spec specifies the "must" behavior you're claiming?

Because what you quoted in comment #1 doesn't.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.