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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jul 11 04:29:13 PDT 2012


           Summary: WebKit doesn't compute relative URLs based on
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh Intel
               URL: http://jigsaw.w3.org/HTTP/CL/
        OS/Version: Mac OS X 10.7
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: brent at architechies.com

RFC 2616 specifies that relative URLs should be computed with the Content-Location, if provided, as the base:


14.14 Content-Location

The Content-Location entity-header field MAY be used to supply the resource location for the entity enclosed in the message when that entity is accessible from a location separate from the requested resource's URI. A server SHOULD provide a Content-Location for the variant corresponding to the response entity; especially in the case where a resource has multiple entities associated with it, and those entities actually have separate locations by which they might be individually accessed, the server SHOULD provide a Content-Location for the particular variant which is returned.

       Content-Location = "Content-Location" ":"
                         ( absoluteURI | relativeURI )

The value of Content-Location also defines the base URI for the entity.


However, WebKit does not appear to do this, at least on the W3C's test case (http://jigsaw.w3.org/HTTP/CL/).

Reproducible with WebKit nightly r122160 on OS X 10.7.3, Safari 7536.6.1 on OS X 10.7.3, and Safari 8536.25 on OS X 10.8 GM seed (12A269).

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

More information about the webkit-unassigned mailing list