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:50:08 +0000
To: public-webapps@w3.org
Message-Id: <E1ObofY-0004PY-Ck@jessica.w3.org>

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
                 CC|                            |bzbarsky@mit.edu
         Resolution|NEEDSINFO                   |

--- Comment #3 from Boris Zbarsky <bzbarsky@mit.edu>  2010-07-22 05:50:07 ---
> ws:foo isn't absolute,

How is a browser supposed to know that?  Trying to create a URI from that
string without a base URI successfully creates one, for example...

> Are browsers not implementing the spec here?

Nope.  Neither Gecko nor webkit throw on such a url, for example.  In Gecko's
case, because the concept of "absolute url" the spec uses (one which resolves
to different things depending on the base) matches nothing that Necko exposes,
and because by the definition normally used in Gecko (it's an absolute URL if
you can parse it as a url even if there is no base) this url is absolute.

See also https://bugzilla.mozilla.org/show_bug.cgi?id=580234 which is what
prompted me to read this section to start with.

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:50:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:10 UTC