Re: Adding user@ to HTTP[S] URIs

Rick van Rein <rick@openfortress.nl> Mon, 27 January 2020 12:32 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87781120033 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 27 Jan 2020 04:32:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.752
X-Spam-Level:
X-Spam-Status: No, score=-2.752 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=openfortress.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4WmdA6Dz3U4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 27 Jan 2020 04:32:09 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CEC0120026 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 27 Jan 2020 04:32:09 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1iw3X2-0001or-Qe for ietf-http-wg-dist@listhub.w3.org; Mon, 27 Jan 2020 12:30:20 +0000
Resent-Date: Mon, 27 Jan 2020 12:30:20 +0000
Resent-Message-Id: <E1iw3X2-0001or-Qe@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <rick@openfortress.nl>) id 1iw3X0-0001lx-LB for ietf-http-wg@listhub.w3.org; Mon, 27 Jan 2020 12:30:18 +0000
Received: from lb1-smtp-cloud9.xs4all.net ([194.109.24.22]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <rick@openfortress.nl>) id 1iw3Wy-0003ws-UJ for ietf-http-wg@w3.org; Mon, 27 Jan 2020 12:30:18 +0000
Received: from popmini.vanrein.org ([83.161.146.46]) by smtp-cloud9.xs4all.net with ESMTP id w3WqiL4m6T6sRw3Wri7tlu; Mon, 27 Jan 2020 13:30:09 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=openfortress.nl; i=rick@openfortress.nl; q=dns/txt; s=fame; t=1580128199; h=message-id : date : from : mime-version : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding : date : from : subject; bh=V/+AtECs3Loz4gFzzs2YgdxoXFnG0fJDrtZDXdkLPO0=; b=jpdH4GchGg2/qyxm/Ua0sh8Qeca2/IF/u9jwM0vuG2eMg6J5gE/KlbW9 DHO0uKmcK2M/xn1aDpLc6CbwoA0701e6E8G9iPogbQgCOY1bcZlZ824NGZ j00UUep5X/x4MZZHIsxbl5nIMu/Ra0Ck1F43goFMgSu8m5GU5om87M1KE=
Received: by fame.vanrein.org (Postfix, from userid 1006) id D50462569B; Mon, 27 Jan 2020 12:29:39 +0000 (UTC)
Received: from airhead.local (phantom.vanrein.org [83.161.146.46]) by fame.vanrein.org (Postfix) with ESMTPA id C8A99254A4; Mon, 27 Jan 2020 12:29:37 +0000 (UTC)
Message-ID: <5E2ED7B0.6040606@openfortress.nl>
Date: Mon, 27 Jan 2020 13:29:36 +0100
From: Rick van Rein <rick@openfortress.nl>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Daniel Stenberg <daniel@haxx.se>
CC: James Fuller <jim@webcomposite.com>, Austin Wright <aaa@bzfx.net>, "HTTPbis WG (IETF)" <ietf-http-wg@w3.org>
References: <5E2B76EC.5000300@openfortress.nl> <BB50C7B7-3861-4054-AFB7-6F1C287AFEE6@gmail.com> <5E2C2039.7080303@openfortress.nl> <0bb7f153-57ea-7cb4-59e2-26ee2e41d928@treenet.co.nz> <5E2C4738.8010609@openfortress.nl> <alpine.DEB.2.20.2001251614520.15685@tvnag.unkk.fr> <5E2C65D7.7030408@openfortress.nl> <4859592D-1B93-49E0-9661-5E24FDAC276F@bzfx.net> <5E2D630A.604@openfortress.nl> <CAEaz5mtYyvei8wxb4_1H36N2PkrU+-47uqn2KtitqMtd9LRwsQ@mail.gmail.com> <5E2ED158.1030909@openfortress.nl> <alpine.DEB.2.20.2001271319120.18042@tvnag.unkk.fr>
In-Reply-To: <alpine.DEB.2.20.2001271319120.18042@tvnag.unkk.fr>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bogosity: Unsure, tests=bogofilter, spamicity=0.520000, version=1.2.4
X-CMAE-Envelope: MS4wfI6u7KuRsSwEZ91BMvDaA8mxOWfDBT3DF2l1EU5UMS4ZtNAQHIZj48OFAN67h91DEKRgxzTuqilqlz+ElX9bl6jw/lPqXJRLUIbeRuz2gkxXnfZBuTVq ZSUzCumeYgBetKk/PzSulNbBwUiRDBXVmPHx1/1fi9v51X1639U8XC/zin6dBNTgGF2bmXpB+ETP6g==
Received-SPF: pass client-ip=194.109.24.22; envelope-from=rick@openfortress.nl; helo=lb1-smtp-cloud9.xs4all.net
X-W3C-Hub-Spam-Status: No, score=-4.8
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1iw3Wy-0003ws-UJ 992ac9a82cdbbcd38ef7191c6e8aa211
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Adding user@ to HTTP[S] URIs
Archived-At: <https://www.w3.org/mid/5E2ED7B0.6040606@openfortress.nl>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37296
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Hi,

Thanks for a technical point, Daniel!

> Maybe not a dragon, but...
>
> $ curl foo@localhost -v
> ...
>> GET / HTTP/1.1
>> Host: localhost
>> Authorization: Basic Zm9vOg==
>
> ... because userinfo in HTTP has only ever been there and used for
> authentication.
>
> (Zm9vOg== is "foo:" base64 encoded)

Browsers have no consistency in this usage pattern, so this is definately a niche.  As a result, nobody would publish such a URI for global purposes, and so there is room to define adaptations to the behaviour.

This Basic hack might be turned into an option, or my draft's form might be; a migration path can easily be started as well.  This is not unexpected when assumptions are made beyond the specs.  Assumptions which, by the way, are the result of wanting to express something for which there is no semantics in the form of a specification.

-Rick