[Bug 10213] 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 on 2011-07-08 (public-html-bugzilla@w3.org from July 2011)

From: <bugzilla@jessica.w3.org>
Date: Fri, 08 Jul 2011 20:05:51 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QfHJ9-0000q3-TS@jessica.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|WebSocket API (editor: Ian  |other Hixie drafts (editor:
                   |Hickson)                    |Ian Hickson)
            Product|WebAppsWG                   |HTML WG
          QAContact|member-webapi-cvs@w3.org    |public-html-bugzilla@w3.org

--- Comment #9 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-07-08 20:05:50 UTC ---
This is a generic platform bug, so I'm moving it out of the WebSockets bucket.

-- 
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 Friday, 8 July 2011 20:05:53 UTC