IETF Logo Mail Archive

Re: Last Call: <draft-levine-herkula-oneclick-04.txt> (Signalling one-click functionality for list email headers) to Proposed Standard (fwd)

Viktor Dukhovni <ietf-dane@dukhovni.org> Wed, 21 September 2016 00:01 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA0CF12B010 for <ietf@ietfa.amsl.com>; Tue, 20 Sep 2016 17:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 DiPdy1_fFIEp for <ietf@ietfa.amsl.com>; Tue, 20 Sep 2016 17:01:07 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F7D0126D74 for <ietf@ietf.org>; Tue, 20 Sep 2016 17:01:06 -0700 (PDT)
Received: from [172.31.24.203] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 7D21C282F88 for <ietf@ietf.org>; Wed, 21 Sep 2016 00:01:05 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Last Call: <draft-levine-herkula-oneclick-04.txt> (Signalling one-click functionality for list email headers) to Proposed Standard (fwd)
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <alpine.OSX.2.11.1609201953210.21755@ary.qy>
Date: Tue, 20 Sep 2016 20:01:05 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <E05F13EC-C8D4-4867-9446-51C83293B535@dukhovni.org>
References: <alpine.OSX.2.11.1609201953210.21755@ary.qy>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QY1EYsrIFEjKWzblvv_gxI4Jz-8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Sep 2016 00:01:09 -0000

> On Sep 20, 2016, at 7:54 PM, John R. Levine <johnl@iecc.com> wrote:
> 
>> There's a reason why browsers send "Origin:" headers, the MUA should
>> do the same when doing POST requests based on email headers.
> 
> MUAs have been doing GETs and, for messages with forms in them, POSTs
> for over a decade.  What origin headers do they send now?  Why is this
> different?

I take no issue with GETs.  The "Origin:" header is comparatively new,
and AFAIK should be present in all POSTs that are triggered via email
content.

Perhaps some of the MUAs that submit forms (sorry, I don't use any that
do) predate "Origin:".  It may also possible that in this context adding
"Origin" is not a useful cross-origin security measure.  I hope someone
more knowlegeable in HTTP security will chime in.

-- 
-- 
	Viktor.

v2.23.0 | Report a Bug | By Email