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

[Bug 10213] [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>
Date: Mon, 18 Jul 2011 21:48:21 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qivfp-0006Qg-Ep@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213

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

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

-- 
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 Monday, 18 July 2011 21:48:26 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:13 UTC