[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-07-27 (public-webapps-bugzilla@w3.org from July 2012)

From: <bugzilla@jessica.w3.org>
Date: Fri, 27 Jul 2012 08:28:24 +0000
To: public-webapps-bugzilla@w3.org
Message-Id: <E1SufuK-0006uv-0B@jessica.w3.org>

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

--- Comment #3 from Julian Reschke <julian.reschke@gmx.de> 2012-07-27 08:28:23 UTC ---
(In reply to comment #1)
> The URL specification needs to define this. This is part of the reason why we
> need a whitelist of hierarchical schemes I think (as most browsers appear to
> have).

It would be good if we had concrete data on which UAs do this, and what for.

-- 
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, 27 July 2012 08:28:25 UTC