W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2020

Re: Adding user@ to HTTP[S] URIs

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 27 Jan 2020 13:32:51 +0100
To: Rick van Rein <rick@openfortress.nl>, Amos Jeffries <squid3@treenet.co.nz>
Cc: ietf-http-wg@w3.org
Message-ID: <fb8e8981-fce5-ac2e-2a4f-43bb487feb71@gmx.de>
On 27.01.2020 13:22, Rick van Rein wrote:
> Hi,
>>> Compatibility with other protocols: You cannot copy/paste your gmail
>>> address to your browser to access it as webmail.
>> Counterpoint: I (and many, many others) cannot do that even with your
>> spec change because the login to my gmail account is a name and domain
>> completely different to the email address URI. A government department
>> is the credentials authority - not Google or '@gmail.com'.
> You are actually _making_ my point :)
> The john.doe@gmail.com represents a resource according to the URI
> specs.  Some HTTP implementations have forcefully tied it to
> Basic/Digest authentication.  My point is that the authentication
> pathway needs a completely different pathway.
> ...

"john.doe@gmail.com" is not a URI; it lacks a scheme. It can be an URI
*reference* which would need a base URI to resolve against.

Best regards, Julian
Received on Monday, 27 January 2020 12:33:58 UTC

This archive was generated by hypermail 2.4.0 : Monday, 27 January 2020 12:33:59 UTC