Re: COPY: "Duplicate" functionality

ChanMaxthon <xcvista@me.com> Tue, 01 November 2016 05:23 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 DB6521294CD for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 31 Oct 2016 22:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.498
X-Spam-Level:
X-Spam-Status: No, score=-8.498 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.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=me.com
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 nVgmBc1iwxPA for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 31 Oct 2016 22:23:05 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 485B1129467 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 31 Oct 2016 22:23:05 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1c1RTa-0002HV-U1 for ietf-http-wg-dist@listhub.w3.org; Tue, 01 Nov 2016 05:19:10 +0000
Resent-Date: Tue, 01 Nov 2016 05:19:10 +0000
Resent-Message-Id: <E1c1RTa-0002HV-U1@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <xcvista@me.com>) id 1c1RTV-0002Dw-Kr for ietf-http-wg@listhub.w3.org; Tue, 01 Nov 2016 05:19:05 +0000
Received: from pv33p03im-asmtp002.me.com ([17.143.180.11]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <xcvista@me.com>) id 1c1RTP-0001rd-JK for ietf-http-wg@w3.org; Tue, 01 Nov 2016 05:19:00 +0000
Received: from process-dkim-sign-daemon.pv33p03im-asmtp002.me.com by pv33p03im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OFY00L006GVG800@pv33p03im-asmtp002.me.com> for ietf-http-wg@w3.org; Tue, 01 Nov 2016 05:18:32 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1477977511; bh=zUk1N91IrNBar+B6xpsFWzU/Uexke6pIz4nVu4WHviM=; h=MIME-version:Content-type:Message-id:From:Subject:Date:To; b=npVfjCnrwLGUssEKqEp0zuLs9Xovqtmte9sa1QDD9rqe3u6iw1h+Zlj5grUwtjjtV bNJW+uVst+bBAB9JHx/VbPdTSUS9vEGsbpC5y6H7/h1C18qelmUWBXQ25WoiV9YupD v1dd5Ho2KqgjNV0tUMbo5Ynx7iTSQoaOgcxLhtOA63jKiwQzz09P7JZmvIgJ3OhJSF jMmVnb/J+weVB7VMtBkupL7VObnAynr/THCc53oljz077DSj+BWxaG9ChF3AjtKJ58 wyLkWpqlprgAQhWo6iq8WN+x5ZGDT9+ii4tOL2hghvQ+V+n30ZXrw7LRsnFdmZind3 Ia4NmkawToXTA==
Received: from [10.50.201.171] (unknown [140.206.89.171]) by pv33p03im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OFY00IIS6QQ7P30@pv33p03im-asmtp002.me.com>; Tue, 01 Nov 2016 05:18:31 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-11-01_02:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1611010094
References: <9104F1BF-CA99-4640-A350-EDE4D9290C84@sharp.fm> <c9f7ee15-cfbb-26f5-4252-d587374f83d5@gmx.de>
MIME-version: 1.0 (1.0)
In-reply-to: <c9f7ee15-cfbb-26f5-4252-d587374f83d5@gmx.de>
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Message-id: <2F51D679-FD66-43E3-9F6C-88947E944371@me.com>
Cc: Graham Leggett <minfrin@sharp.fm>, HTTP Working Group <ietf-http-wg@w3.org>
X-Mailer: iPhone Mail (13G29)
From: ChanMaxthon <xcvista@me.com>
Date: Tue, 01 Nov 2016 13:18:25 +0800
To: Julian Reschke <julian.reschke@gmx.de>
Received-SPF: pass client-ip=17.143.180.11; envelope-from=xcvista@me.com; helo=pv33p03im-asmtp002.me.com
X-W3C-Hub-Spam-Status: No, score=-7.2
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.505, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1c1RTP-0001rd-JK cbe48ef3f42f47d016b0ac2a64e5e7c1
X-Original-To: ietf-http-wg@w3.org
Subject: Re: COPY: "Duplicate" functionality
Archived-At: <http://www.w3.org/mid/2F51D679-FD66-43E3-9F6C-88947E944371@me.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32778
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: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

I think you can generate a name, HEAD it, and then COPY it if you get a 404.

Sent from my iPhone

> On Nov 1, 2016, at 02:10, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
>> On 2016-10-31 18:49, Graham Leggett wrote:
>> Hi all,
>> 
>> According to https://tools.ietf.org/html/rfc4918#section-9.8, the COPY method allows me to make a copy of a resource, but only as long as I know the destination URL of my copy: "The Destination header MUST be present.”.
>> 
>> What I need to implement is functionality that matches the “Duplicate” menu item in the MacOS Finder. In other words, I want to make a copy of an URL, but I want the server to decide on the URL to the COPY.
>> 
>> Is this possible while at the same time being RFC compliant?
>> 
>> If I was to set the Destination header to the same URL as the source, or perhaps the parent collection of the source, would that make sense?
>> 
>> Regards,
>> Graham
> 
> Well, there is no standard functionality for that. You can sure experiment if you control both client and server (I'd probably try "path/*" as destination URI).
> 
> Best regards, Julian
> 
>