W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

[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>
Date: Thu, 22 Jul 2010 05:39:44 +0000
To: public-webapps@w3.org
Message-Id: <E1OboVU-0003qz-Av@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213


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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |NEEDSINFO




--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-07-22 05:39:43 ---
ws:foo isn't absolute, therefore per spec it's treated as non-absolute. Am I
missing something? Are browsers not implementing the spec here?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 22 July 2010 05:39:45 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:40 GMT