W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2010

[Bug 10213] New: The definition of "absolute url" makes https:foo not an absolute url, since its behavior depends on whether the base is https: or not. Is that desired? In particular, using this definition for websockets means that wss: urls with no forward slashes afte

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Jul 2010 20:37:21 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-10213-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213

           Summary: The definition of "absolute url" makes https:foo not
                    an absolute url, since its behavior depends on whether
                    the base is https: or not.  Is that desired?  In
                    particular, using this definition for websockets means
                    that wss: urls with no forward slashes afte
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#abs
                    olute-url
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org


Section: http://www.whatwg.org/specs/web-apps/current-work/#absolute-url

Comment:
The definition of "absolute url" makes https:foo not an absolute url, since
its behavior depends on whether the base is https: or not.  Is that desired? 
In particular, using this definition for websockets means that wss: urls with
no forward slashes after the ':' are treated as non-absolute, though in fact
they're treated as absolute by the browser in practice.

Posted from: 173.48.34.3

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 20 July 2010 20:37:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:52 UTC