[Bug 17772] [URL] 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... from bugzilla@jessica.w3.org on 2012-09-28 (public-webapps-bugzilla@w3.org from September 2012)

From: <bugzilla@jessica.w3.org>
Date: Fri, 28 Sep 2012 10:43:57 +0000
To: public-webapps-bugzilla@w3.org
Message-Id: <E1THY33-0000yH-94@jessica.w3.org>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17772

Anne <annevk@annevk.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #5 from Anne <annevk@annevk.nl> 2012-09-28 10:43:56 UTC ---
http://url.spec.whatwg.org/ defines this behaviour now and makes browsers'
behavior for ws/wss conforming. All that is left here is updating the WebSocket
API to refer to the new URL standard.

-- 
Configure bugmail: https://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, 28 September 2012 10:44:02 UTC