Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 71286 invoked from network); 1 Aug 2000 19:58:20 -0000 Received: from hplb.hpl.hp.com (192.6.10.2) by locus.apache.org with SMTP; 1 Aug 2000 19:58:20 -0000 Received: from snowy.hpl.hp.com (snowy.hpl.hp.com [15.144.94.243]) by hplb.hpl.hp.com (8.9.3/8.8.6 HPLabs Bristol Relay) with ESMTP id UAA21803 for ; Tue, 1 Aug 2000 20:58:16 +0100 (BST) Received: from cvwls095 ([15.0.214.208]) by snowy.hpl.hp.com with SMTP (8.7.6/8.7.3 SMKit7.0) id UAA25591 for ; Tue, 1 Aug 2000 20:58:14 +0100 (BST) Message-ID: <01ba01bffbf2$f0883920$d0d6000f@cvwls095> From: "Steve Loughran" To: References: <2561BD1655ADD2119E230008C75D96A904527703@emily.barclaycard.co.uk><3.0.5.32.20000801224045.009036d0@latcs2.cs.latrobe.edu.au> Subject: Re: FTP & JSPC Date: Tue, 1 Aug 2000 12:59:00 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Stefan Bodewig" To: Sent: Tuesday, August 01, 2000 05:50 Subject: Re: FTP & JSPC > I think we should base a PUT task on WebDAV rather than HTTP PUT alone. I am still not 100% clear what the diffs between HTTP/1.1 PUT and webdav PUT are. I think they are:- -webDav clients should lock the resource first, unlock it afterwards and include the lock key in the PUT request -webdav clients and servers should support more secure alternatives to basic-auth, such as message digest authentication The question is, how much of that is needed right now -specifcally, what do the servers (especially apache with mod_dav1.0) expect? -Steve