From w3c-dist-auth-request@w3.org Mon Oct 2 07:59:26 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA06152 for ; Mon, 2 Oct 2000 07:59:25 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id HAA03233; Mon, 2 Oct 2000 07:54:31 -0400 (EDT) Resent-Date: Mon, 2 Oct 2000 07:54:31 -0400 (EDT) Resent-Message-Id: <200010021154.HAA03233@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id HAA03208 for ; Mon, 2 Oct 2000 07:54:26 -0400 (EDT) Received: from yosemite.rwc.gnac.net (yosemite.rwc.gnac.net [198.151.248.221]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id HAA26847 for ; Mon, 2 Oct 2000 07:54:27 -0400 Received: by yosemite.rwc.gnac.net; id EAA02389; Mon, 2 Oct 2000 04:56:41 -0700 (PDT) Received: from unknown(192.168.5.22) by yosemite.rwc.gnac.net via smap (V5.0) id xma002374; Mon, 2 Oct 00 04:56:15 -0700 Received: from tweety.main.gnac.com (localhost.gnac.net [127.0.0.1]) by pepe.ops.rwc.gnac.net (8.11.0/8.8.7/GNAC-GW-2.1) with ESMTP id e92BrfJ21494; Mon, 2 Oct 2000 04:53:41 -0700 (PDT) Received: from cr1012300a (dialin30.main.gnac.com [192.168.3.30]) by tweety.main.gnac.com (8.9.3/8.7.3/GNAC-COM-1.1) with SMTP id EAA13287; Mon, 2 Oct 2000 04:53:54 -0700 (PDT) Message-ID: <004501c02c70$aefb7bd0$1e03a8c0@cr1012300a> From: "S. Matthew Hersey" To: Cc: References: <8025696C.0032AEC0.00@d06mta07.portsmouth.uk.ibm.com> Date: Mon, 2 Oct 2000 08:59:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 Disposition-Notification-To: "S. Matthew Hersey" X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Subject: Re: More on More on "Webify Word? No Way!" Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4404 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit ----- Original Message ----- From: To: "[WEB-IDEAS] LISTMASTER" Cc: Sent: Monday, October 02, 2000 5:13 AM Subject: Re: More on "Webify Word? No Way!" Matthew, I read and re-read your post, but couldn't quite figure out what position you were taking on Word. The IETF require the document submissions to be simple ASCII texts, however you can appreciate that editing a living document in this fashion is significantly more work than using the facilities of a word processor. The advantage is that it produces various forms of output -- I prefer to review the Word version as I find it more readable, and Word can produce the ASCII format required by IETF. As Geoff points out, Word also supports WebFolders for collaborative authoring, and it faithfully follows WebDAV RFC2518 in this respect. Don't confuse the fact that Word uses XML in its source with its use of WebDAV protocol. Regards, Tim ====================================================== Heya Tim, Thanks for taking the time to consider my comments. To clarify my position on MS Word vis-a-vis your observations: Authoring Documents in Word and using Word as a tool to generate nicely formatted ASCII text documents (because it is easier that hacking raw ASCII text into shape)...ok Word implements XML and uses WebDAV...OK Word Documents are are easier to review because they are easier to read...depends. -Read-only Internet access (viewing) for Word doc betas via Web browser is restrictive. -Yes, Word can also convert docs to MSO markup laden HTML, but the redundant code links to oblivion, and this can result in fatal errors to a variety of Web browsers and Operating Systems. The size of these files wastes bandwidth. -Caution: Abuse of Word's Standard Dictionary for spell-checking documents prior to publishing can result in SDD Syndrome. *My Experience With SDDS* I am suffering from "The Standard Dictionary Dependency Syndrome" due to Word Spell Check abuse. I was once a Spelling Bee Champion, but not anymore. Over the course of my publishing career, I have relied extensively on Microsoft (R) Word as my primary WordProcessing Application. Recently, I began to challenge myself to limit my daily use of Spell Check. A short time later, I experienced a Satori where I actualized my inability to spell without it in many cases. Outlook Express, which features scaled down Word-style WYSIWYG Authoring, has a similar Spell Check feature. I decided to cut down on my Outlook Express usage drastically. I began to use the Eudora Lite V.3 Email Client (no spell checker) to recompile and roll back to the working version of spelling skills that I flaunted in grade school. Thinking back, the degradation of stored information and available resources in my own "internal" database appears to correlate with my initial discovery in Grad School, (and long-term exploitation) of the ever-expanding Standard Dictionary in Microsoft Word, Outlook, and Outlook Express. I attempted to spell-check my email messages manually. This proved to be a fiasco. Thus, what seemed, at the outset, to be a logical step in attempting to rectify a consequence of my software dependency, has now resulted in a exposing a quality flaw in my workflow productivity process. I began to concentrate on how to nip this issue in the bud, without initiating a relapse into Spell Check Dependency. I am now sending my email from the old Eudora client, using an alternate account, to myself@mystandard.com. I then download the messages using Outlook Express, and perform the standard Quality Assurance testing on their content before sending them off to the intended recipient. Integrating Eudora into the "Email Engineering Process" as a Poka-Yoke, has proven slightly more time consuming. Nevertheless, the addition of this step meets the requirements for counteracting the long-term effects of overexposure to Word. I am submitting myself to this spell-therapy process in the hope that a gradual recovery from SDDS will be affected. Perhaps "The Standard Dictionary Dependency Syndrome" will be recognized as a parallel issue, and one that may have been overlooked in the discussion of Word as a webDAV client/Document Authoring Tool. In the 5 Ss of Desktop Kaizen, safety (both physical and intellectual) remains as the primary concern. Regards, smh S. Matthew Hersey, MA Ed. Technical Writer, Operations Certainty Solutions, Inc. "Certainty in an Uncertain World" From w3c-dist-auth-request@w3.org Mon Oct 2 14:50:39 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12384 for ; Mon, 2 Oct 2000 14:50:37 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id OAA20605; Mon, 2 Oct 2000 14:41:45 -0400 (EDT) Resent-Date: Mon, 2 Oct 2000 14:41:45 -0400 (EDT) Resent-Message-Id: <200010021841.OAA20605@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id OAA20583 for ; Mon, 2 Oct 2000 14:41:39 -0400 (EDT) Received: from services.cse.ucsc.edu (services.cse.ucsc.edu [128.114.48.10]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id OAA02584 for ; Mon, 2 Oct 2000 14:41:39 -0400 Received: from galileo (dhcp-63-142.cse.ucsc.edu [128.114.63.142]) by services.cse.ucsc.edu (8.9.1a/8.9.1) with SMTP id LAA25131 for ; Mon, 2 Oct 2000 11:41:32 -0700 (PDT) From: "Jim Whitehead" To: "WebDAV WG" Date: Mon, 2 Oct 2000 11:40:50 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Subject: FW: [Moderator Action] Re: More on "Webify Word? No Way!" Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4405 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Accidentally caught by the spam filter (though Matthew quoted this message in his response, so you may have already seen it...) - Jim -----Original Message----- From: Tim_Ellison@uk.ibm.com [mailto:Tim_Ellison@uk.ibm.com] Sent: Monday, October 02, 2000 2:14 AM To: [WEB-IDEAS] LISTMASTER Cc: w3c-dist-auth@w3.org Subject: [Moderator Action] Re: More on "Webify Word? No Way!" Matthew, I read and re-read your post, but couldn't quite figure out what position you were taking on Word. The IETF require the document submissions to be simple ASCII texts, however you can appreciate that editing a living document in this fashion is significantly more work than using the facilities of a word processor. The advantage is that it produces various forms of output -- I prefer to review the Word version as I find it more readable, and Word can produce the ASCII format required by IETF. As Geoff points out, Word also supports WebFolders for collaborative authoring, and it faithfully follows WebDAV RFC2518 in this respect. Don't confuse the fact that Word uses XML in its source with its use of WebDAV protocol. Regards, Tim "[WEB-IDEAS] LISTMASTER" on 2000-09-29 05:45:51 PM Please respond to "[WEB-IDEAS] LISTMASTER" To: "WEB - IDEAS" cc: "'WebDAV WG'" (bcc: Tim Ellison/UK/IBM) Subject: More on "Webify Word? No Way!" More on WebDAV: http://www.webdav.org/deltav/protocol/draft-ietf-deltav-versioning-08.htm (co-authored by Christopher Kaller of Microsoft) Look at the source code: For those of us who question why this Internet Draft html would be published Microsoft Word: WebDAV conventiently stores all resource properties in an XML document. WebDAV (and now DeltaV) is being developed to use MSIE5+ as a front end in conjunction with the Windows 2000 platform Web Folders feature acting as a remote client. JimWhitehead, Chair of the webDAV Working Group and Assistant Professor of Software Engineering at UCSC (http://www.ics.uci.edu/~ejw/papers/whitehead_diss.pdf)e xplains that the goal of the new DeltaV protocol is to take out "a lock on the resource, write its contents, write the property, then unlock". He goes on to say that if you "wanted to add this property capability for a third-party client, like Word, then you're currently out of luck". So why author the Web version of the the document linked above in Word? Again we ought to refer to the source code: Geoffrey Clemm, Jim Amsden, Christopher Kaler, Jim Whitehead Geoffrey Clemm 2 0 2000-07-07T16:26:00Z 2000-09-11T16:53:00Z 2000-09-11T16:53:00Z 61 19456 110903 World Wide Web Consortium 924 221 136196 9.3821 MS Word 2000 embeds version data into the head of the document using the MSO markup flavor of XML. Word autolocks a document that is under development so that one user, or group member is editing it at a time. When the editor is finished writing, saves the document and closes it, the version data is embedded. When the document is closed, it is unlocked and another user or group member can continue its development. Word is an effective authoring and version control application for Internet publishing. Web pages authored in Word are kind of crufty. This author hopes that WebDav will eliminate the need to rely on Word to control authoring and versioning for Web document publishing. S. Matthew Hersey, MA Ed. Technical Writer, Operations Certainty Solutions, Inc. "Certainty in an Uncertain World" From w3c-dist-auth-request@w3.org Tue Oct 3 10:11:01 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA12001 for ; Tue, 3 Oct 2000 10:11:01 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id KAA26287; Tue, 3 Oct 2000 10:00:24 -0400 (EDT) Resent-Date: Tue, 3 Oct 2000 10:00:24 -0400 (EDT) Resent-Message-Id: <200010031400.KAA26287@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id KAA26244 for ; Tue, 3 Oct 2000 10:00:16 -0400 (EDT) Received: from gw.atria.com (gw.atria.com [192.88.237.2]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id KAA30716; Tue, 3 Oct 2000 10:00:15 -0400 Received: from 204.167.8.157 (tantalum.atria.com) by gw.atria.com id Tue, 3 Oct 2000 10:00:15 -0400 (EDT) Received: (from gclemm@localhost) by tantalum.atria.com (8.8.8+Sun/8.8.8) id JAA06438; Tue, 3 Oct 2000 09:59:46 -0400 (EDT) Date: Tue, 3 Oct 2000 09:59:46 -0400 (EDT) Message-Id: <200010031359.JAA06438@tantalum.atria.com> X-Authentication-Warning: tantalum.atria.com: gclemm set sender to geoffrey.clemm@rational.com using -f From: "Geoffrey M. Clemm" To: w3c-dist-auth@w3.org, ietf-dav-versioning@w3.org In-reply-to: References: Subject: Re: DeltaV: protocol nearing last call Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4406 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Just as a heads up: The last call document is version 09 http://www.webdav.org/deltav/protocol/draft-ietf-deltav-versioning-09.htm (soon to be also available in the standard text format in the standard internet draft location at www.ietf.org). I actually didn't get the 09 draft up until Sunday, Oct 1, figuring that nobody would actually download it over the weekend ... not counting on the extraordinary diligence of working group members like Lisa Dusseault, who *did* in fact download the old draft (08) over the weekend. I have moved the 08 draft to an "old" subdirectory, to make sure nobody else clicks on the 08 reference in Jim's message and gets the older draft. Cheers, Geoff From: "Jim Whitehead" As many of you know, the IETF DeltaV working group was formed to extend HTTP/DAV with versioning and configuration management capabilities, completing the original goal of the WebDAV working group. Some call it putting the "V" back into WebDAV (of course, I don't think it ever left :-). DeltaV has been developing a protocol document, "Versioning Extensions to WebDAV", , available at: http://www.webdav.org/deltav/protocol/draft-ietf-deltav-versioning-08.htm The protocol encompasses the ability to check-in and check-out resources, view the history tree, create private workspaces, group changes into activities, and develop configurations. It introduces several new HTTP methods, including REPORT, VERSION-CONTROL, CHECKOUT, CHECKIN, UNCHECKIN, SET-TARGET, LABEL, MKWORKSPACE, MKACTIVITY, BASELINE-CONTROL, and MERGE. It also introduces several new WebDAV properties, and has an associated versioning data model. Jim Amsden, the chair of DeltaV, has stated that the DeltaV versioning protocol is going to begin a working group last call period at the end of September, thus indicating that the protocol document is stable, has resolved existing design choices, and is at a good point to receive broad community review. If you would like to examine this protocol, and provide feedback now, when it is still relatively easy to make changes, I encourage you to read the latest I-D (or working draft), and submit comments to the DeltaV mailing list. The DeltaV working group home page is: http://www.webdav.org/deltav/ The DeltaV mailing list is: ietf-dav-versioning@w3.org -- send a message with subject line of "subscribe" to ietf-dav-versioning-request@w3.org. - Jim From w3c-dist-auth-request@w3.org Tue Oct 3 14:14:39 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA20197 for ; Tue, 3 Oct 2000 14:14:39 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id OAA07084; Tue, 3 Oct 2000 14:03:24 -0400 (EDT) Resent-Date: Tue, 3 Oct 2000 14:03:24 -0400 (EDT) Resent-Message-Id: <200010031803.OAA07084@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id OAA07038 for ; Tue, 3 Oct 2000 14:03:18 -0400 (EDT) Received: from sus-ma1it00.rational.com (ext-38159.rational.com [192.229.38.159]) by tux.w3.org (8.9.3/8.9.3) with SMTP id OAA23597; Tue, 3 Oct 2000 14:03:14 -0400 Received: from 192.168.215.70 by sus-ma1it00.rational.com (InterScan E-Mail VirusWall NT); Tue, 03 Oct 2000 14:01:28 -0400 (Eastern Daylight Time) Received: by sus-ma1it00.rational.com with Internet Mail Service (5.5.2650.21) id ; Tue, 3 Oct 2000 14:01:28 -0400 Message-ID: <3906C56A7BD1F54593344C05BD1374B10D9ED6@SUS-MA1IT01> From: "Clemm, Geoff" To: w3c-dist-auth@w3.org, ietf-dav-versioning@w3.org Date: Tue, 3 Oct 2000 14:01:09 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Subject: DeltaV: protocol last call Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4407 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: I will be trying to keep up a "working document" for the versioning protocol, that includes any changes to the protocol based upon the last call comments. Whenever a new "working document" is available, I will post a message to the ietf-dav-versioning@w3.org mailing list (which is the mailing list to which all last call comments on the versioning draft should be posted). Anyone that is planning on making comments is encouraged to download the most recent working document, so that you don't run into typos/issues that have been already been addressed. But note that if you are in the middle of making comments on a draft, feel free to ignore any working versions that get announced, since you shouldn't have to spend time "carrying forward" your comments from one draft to the next (I'll take care of that). And I'll take this opportunity to announce the first last call update: 09.1 http://www.webdav.org/deltav/protocol/draft-ietf-deltav-versioning-09.1.htm This version has changes based on reviews from Boris and Tim. In particular, the term "version URL" has been cleaned out of the draft, and a set of advanced versioning OPTIONS "clusters" have been added. Cheers, Geoff -----Original Message----- From: Geoffrey M. Clemm [mailto:geoffrey.clemm@rational.com] Sent: Tuesday, October 03, 2000 10:00 AM To: w3c-dist-auth@w3.org; ietf-dav-versioning@w3.org Subject: Re: DeltaV: protocol nearing last call Just as a heads up: The last call document is version 09 http://www.webdav.org/deltav/protocol/draft-ietf-deltav-versioning-09.htm (soon to be also available in the standard text format in the standard internet draft location at www.ietf.org). I actually didn't get the 09 draft up until Sunday, Oct 1, figuring that nobody would actually download it over the weekend ... not counting on the extraordinary diligence of working group members like Lisa Dusseault, who *did* in fact download the old draft (08) over the weekend. I have moved the 08 draft to an "old" subdirectory, to make sure nobody else clicks on the 08 reference in Jim's message and gets the older draft. Cheers, Geoff From: "Jim Whitehead" As many of you know, the IETF DeltaV working group was formed to extend HTTP/DAV with versioning and configuration management capabilities, completing the original goal of the WebDAV working group. Some call it putting the "V" back into WebDAV (of course, I don't think it ever left :-). DeltaV has been developing a protocol document, "Versioning Extensions to WebDAV", , available at: http://www.webdav.org/deltav/protocol/draft-ietf-deltav-versioning-08.htm The protocol encompasses the ability to check-in and check-out resources, view the history tree, create private workspaces, group changes into activities, and develop configurations. It introduces several new HTTP methods, including REPORT, VERSION-CONTROL, CHECKOUT, CHECKIN, UNCHECKIN, SET-TARGET, LABEL, MKWORKSPACE, MKACTIVITY, BASELINE-CONTROL, and MERGE. It also introduces several new WebDAV properties, and has an associated versioning data model. Jim Amsden, the chair of DeltaV, has stated that the DeltaV versioning protocol is going to begin a working group last call period at the end of September, thus indicating that the protocol document is stable, has resolved existing design choices, and is at a good point to receive broad community review. If you would like to examine this protocol, and provide feedback now, when it is still relatively easy to make changes, I encourage you to read the latest I-D (or working draft), and submit comments to the DeltaV mailing list. The DeltaV working group home page is: http://www.webdav.org/deltav/ The DeltaV mailing list is: ietf-dav-versioning@w3.org -- send a message with subject line of "subscribe" to ietf-dav-versioning-request@w3.org. - Jim From w3c-dist-auth-request@w3.org Mon Oct 9 08:28:41 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA02557 for ; Mon, 9 Oct 2000 08:28:41 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id IAA24992; Mon, 9 Oct 2000 08:20:16 -0400 (EDT) Resent-Date: Mon, 9 Oct 2000 08:20:16 -0400 (EDT) Resent-Message-Id: <200010091220.IAA24992@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id IAA24955 for ; Mon, 9 Oct 2000 08:20:11 -0400 (EDT) Received: from e21.nc.us.ibm.com (e21.nc.us.ibm.com [32.97.136.227]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id IAA12116; Mon, 9 Oct 2000 08:20:09 -0400 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e21.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id IAA123500; Mon, 9 Oct 2000 08:07:37 -0500 Received: from d04nms03.raleigh.ibm.com (d04nms03nms04.raleigh.ibm.com [9.67.228.68]) by southrelay02.raleigh.ibm.com (8.8.8m3/NCO v4.93) with ESMTP id IAA24358; Mon, 9 Oct 2000 08:20:02 -0400 To: ietf-dav-versioning@w3.org, w3c-dist-auth@w3.org X-Mailer: Lotus Notes Release 5.0.2a November 23, 1999 Message-ID: From: "Jim Amsden/Raleigh/IBM" Date: Mon, 9 Oct 2000 08:10:20 -0400 X-MIMETrack: Serialize by Router on D04NMS03/04/M/IBM(Release 5.0.3 (Intl)|21 March 2000) at 10/09/2000 08:20:01 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: DeltaV Working Group Last Call Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4408 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: *** WORKING GROUP LAST CALL FOR COMMENTS *** WebDAV Versioning and Configuration Management PROTOCOL SPECIFICATION This is the final call for comments from the DeltaV working group on the WebDAV Versioning and Configuration Management Specification, draft-ietf-deltav-versioning-10. This last call for comments period begins immediately, and ends December 1, 2000, at midnight, US Eastern time. This allows just over seven weeks for review of the specification in time for the December IETF '49 meeting. At the end of the last call review period, a new draft will be issued. Depending on the scope of changes introduced between the -10 and -11 versions, there will either be an immediate call for rough consensus (very few changes), or a second last call review period (significant changes). Once the document represents the rough consensus of the working group, I will submit this document to the Internet Engineering Steering Group (IESG) for their approval. IESG review involves a (minimum) two week public last call for comments period. This IESG-initiated last call period is in addition to the working group last call period. This document is intended to be a "Proposed Standard". Quoting from RFC 2026, "The Internet Standards Process -- Revision 3": The entry-level maturity for the standards track is "Proposed Standard". A specific action by the IESG is required to move a specification onto the standards track at the "Proposed Standard" level. A Proposed Standard specification is generally stable, has resolved known design choices, is believed to be well-understood, has received significant community review, and appears to enjoy enough community interest to be considered valuable. However, further experience might result in a change or even retraction of the specification before it advances. Usually, neither implementation nor operational experience is required for the designation of a specification as a Proposed Standard. However, such experience is highly desirable, and will usually represent a strong argument in favor of a Proposed Standard designation. Many details on the procedures used to develop an IETF standard can be found in RFC 2026, available at: http://www.ietf.org/rfc/rfc2026.txt If there are any procedural questions or concerns, please do not hesitate to contact me, or raise an issue on the list. Notes: 1) Issues raised during the last call period will be resolved individually, rather than lumped together and dealt with as a whole. This follows the issue-resolution convention being followed in the HTTP WG. 2) If you've been waiting for a "stable" version of the specification before performing a review, you need wait no longer. This is it. We value your input, but time is running out. So please review the specification now in order to ensure your input gets included. - Jim Amsden Chair, IETF DeltaV Working Group From w3c-dist-auth-request@w3.org Mon Oct 9 14:37:48 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA07936 for ; Mon, 9 Oct 2000 14:37:47 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id OAA08218; Mon, 9 Oct 2000 14:29:07 -0400 (EDT) Resent-Date: Mon, 9 Oct 2000 14:29:07 -0400 (EDT) Resent-Message-Id: <200010091829.OAA08218@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id OAA08198 for ; Mon, 9 Oct 2000 14:29:03 -0400 (EDT) Received: from kovsjexchange.kovair.com (unnamed.kovair.com [63.112.189.161] (may be forged)) by tux.w3.org (8.9.3/8.9.3) with ESMTP id OAA10306 for ; Mon, 9 Oct 2000 14:29:03 -0400 Received: by KOVSJEXCHANGE with Internet Mail Service (5.5.2650.21) id <4P2YAFK6>; Mon, 9 Oct 2000 11:29:12 -0700 Message-ID: <936091CF9671D4118BEF00508BAC4B0C0C7DF6@KOVSJEXCHANGE> From: Madan Mohan To: "'w3c-dist-auth@w3.org'" Date: Mon, 9 Oct 2000 11:29:12 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Subject: webFolders PUT Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4409 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Hi I am writing a Java servlet which listens to WEBDAV reqests and responds to them. Using web folders as my client. I am able to create and delete folders. The problem comes when i drag and drop a file from my local disk into the web folder. My sniffer says that web folders makes a head and put and head. Now the PUT has content length of 0. HAve i done something wrong here. So how to I copy the file to the server when web folders does not send me the file data. What response should i give for this PUT with 0 content length? MAdan From w3c-dist-auth-request@w3.org Mon Oct 9 14:59:51 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08302 for ; Mon, 9 Oct 2000 14:59:44 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id OAA08945; Mon, 9 Oct 2000 14:47:30 -0400 (EDT) Resent-Date: Mon, 9 Oct 2000 14:47:30 -0400 (EDT) Resent-Message-Id: <200010091847.OAA08945@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id OAA08925 for ; Mon, 9 Oct 2000 14:47:27 -0400 (EDT) Received: from neo.neographic.com ([209.143.245.222]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id OAA11631 for ; Mon, 9 Oct 2000 14:47:23 -0400 Received: from LALA.carpenter.ORG (Filenet-gw.filenet.com [198.3.8.1]) by neo.neographic.com (8.9.1a/8.8.4) with SMTP id OAA13060; Mon, 9 Oct 2000 14:46:34 -0400 (EDT) Date: Mon, 9 Oct 2000 11:49:10 -0700 Message-ID: <32-Mon09Oct2000114910-0700-bill@carpenter.ORG> X-Mailer: 21.1 (patch 9) "Canyonlands" XEmacs Lucid (via feedmail 9-beta-13 I) wjc loop; VM 6.71 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: bill@carpenter.ORG (WJCarpenter) To: w3c-dist-auth@w3.org In-Reply-To: <936091CF9671D4118BEF00508BAC4B0C0C7DF6@KOVSJEXCHANGE> References: <936091CF9671D4118BEF00508BAC4B0C0C7DF6@KOVSJEXCHANGE> Subject: RE: webFolders PUT Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4410 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit madan> I am writing a Java servlet which listens to WEBDAV reqests and madan> responds to them. Using web folders as my client. I am able to madan> create and delete folders. The problem comes when i drag and madan> drop a file from my local disk into the web folder. My sniffer madan> says that web folders makes a head and put and head. Now the madan> PUT has content length of 0. HAve i done something wrong madan> here. So how to I copy the file to the server when web folders madan> does not send me the file data. What response should i give for madan> this PUT with 0 content length? My advice is to make a zero-length file and declare success. After all, it's completely legal. Web Folders is trying to make sure it can create the file before it sends the content. You didn't say, but usually the sequence you mentioned is quickly followed by another PUT with the real content. Someone locally suggested that Web Folders does it this seemingly zany way to emulate the way MSWindows implementations deal with local file systems. It doesn't cost much with local file systems to do it that way. -- bill@carpenter.ORG (WJCarpenter) PGP 0x91865119 38 95 1B 69 C9 C6 3D 25 73 46 32 04 69 D6 ED F3 From w3c-dist-auth-request@w3.org Mon Oct 9 17:18:53 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10062 for ; Mon, 9 Oct 2000 17:18:52 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id RAA12301; Mon, 9 Oct 2000 17:10:14 -0400 (EDT) Resent-Date: Mon, 9 Oct 2000 17:10:14 -0400 (EDT) Resent-Message-Id: <200010092110.RAA12301@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id RAA12280 for ; Mon, 9 Oct 2000 17:10:10 -0400 (EDT) Received: from kovsjexchange.kovair.com (unnamed.kovair.com [63.112.189.161] (may be forged)) by tux.w3.org (8.9.3/8.9.3) with ESMTP id RAA21893 for ; Mon, 9 Oct 2000 17:10:10 -0400 Received: by KOVSJEXCHANGE with Internet Mail Service (5.5.2650.21) id <4P2YAFWR>; Mon, 9 Oct 2000 14:09:57 -0700 Message-ID: <936091CF9671D4118BEF00508BAC4B0C0C7DF8@KOVSJEXCHANGE> From: Madan Mohan To: "'w3c-dist-auth@w3.org'" Cc: "'bill@carpenter.org'" Date: Mon, 9 Oct 2000 14:09:56 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C03235.46BA7D3A" Subject: webFolders PUT Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4411 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C03235.46BA7D3A Content-Type: text/plain; charset="iso-8859-1" <> Hi Bill This is my Sniff file. No case problems Madan ------_=_NextPart_000_01C03235.46BA7D3A Content-Type: application/octet-stream; name="Snif1.cap" Content-Disposition: attachment; filename="Snif1.cap" Content-Transfer-Encoding: base64 WENQADAwMi4wMDEAtjPiORsAAAAAAIAAgAAAAKQQAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAA AAAAAOH1BQAAAAAAAAAAFAAEAN40EgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAADFgqoAAAAAADwAPAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAED H5E8AAEDIbvnCABFAAAsFwhAAIAGzMkKAQFnCgEBkgTRAFAA5TDQAAAAAGACIAAqVgAAAgQFtAAA ZYOqAAAAAAA8ADwAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAABAyG75wABAx+RPAgARQAA LJwCQACABkfPCgEBkgoBAWcAUATRAAwq6gDlMNFgEiI4/RYAAAIEBbQAANGDqgAAAAAAPAA8AAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQMfkTwAAQMhu+cIAEUAACgYCEAAgAbLzQoBAWcK AQGSBNEAUADlMNEADCrrUBAiOBTUAAAAAAAAAACohKoAAAAAABABEAEAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAEDH5E8AAEDIbvnCABFAAECGQhAAIAGyfMKAQFnCgEBkgTRAFAA5TDRAAwq 61AYIjizDAAASEVBRCAvdGVzdC5odG1sIEhUVFAvMS4xDQpBY2NlcHQtTGFuZ3VhZ2U6IGVuLXVz DQpUcmFuc2xhdGU6IGYNCkNvbnRlbnQtTGVuZ3RoOiAwDQpVc2VyLUFnZW50OiBNaWNyb3NvZnQg RGF0YSBBY2Nlc3MgSW50ZXJuZXQgUHVibGlzaGluZyBQcm92aWRlciBEQVYNCkhvc3Q6IG1tb2hh bg0KQ29ubmVjdGlvbjogS2VlcC1BbGl2ZQ0KQXV0aG9yaXphdGlvbjogQmFzaWMgYlRwdA0KDQr0 3KoAAAAAAE4ATgAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAEDIbvnAAEDH5E8CABFAABA nQJAAIAGRrsKAQGSCgEBZwBQBNEADCrrAOUxq1AYIV4vWQAASFRUUC8xLjAgNDA0IE5vdCBGb3Vu ZA0KEuiqAAAAAAAfAR8BAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAABAyG75wABAx+RPAgA RQABEZ4CQACABkTqCgEBkgoBAWcAUATRAAwrAwDlMatQGSFerrsAAERhdGU6IE1vbiwgMDkgT2N0 IDIwMDAgMjE6MDg6MTcgR01UDQpTZXJ2bGV0LUVuZ2luZTogVG9tY2F0IFdlYiBTZXJ2ZXIvMy4x IFJDMSAoSlNQIDEuMTsgU2VydmxldCAyLjI7IEphdmEgMS4yLjI7IFdpbmRvd3MgTlQgNC4wIHg4 NjsgamF2YS52ZW5kb3I9U3VuIE1pY3Jvc3lzdGVtcyBJbmMuKQ0KQ29udGVudC1MYW5ndWFnZTog ZW4NCkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbg0KU3RhdHVzOiA0MDQNCg0KqOiqAAAAAAA8ADwA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAx+RPAABAyG75wgARQAAKBoIQACABsnNCgEB ZwoBAZIE0QBQAOUxqwAMK+1QECE3E/kAAAAAAAAAAD3pqgAAAAAAPAA8AAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAQMfkTwAAQMhu+cIAEUAACgbCEAAgAbIzQoBAWcKAQGSBNEAUADlMasA DCvtUBEhNxP4AAAAAAAAAABv6aoAAAAAADwAPAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAA AAEDIbvnAAEDH5E8CABFAAAonwJAAIAGRNMKAQGSCgEBZwBQBNEADCvtAOUxrFAQIV4T0QAAAAAA AAAAVgGrAAAAAAA8ADwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAx+RPAABAyG75wgA RQAALBwIQACABsfJCgEBZwoBAZIE0gBQAOUxLAAAAABgAiAAKfkAAAIEBbQAAEsCqwAAAAAAPAA8 AAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAQMhu+cAAQMfkTwIAEUAACygAkAAgAZDzwoB AZIKAQFnAFAE0gAMKzAA5TEtYBIiOPxzAAACBAW0AAC0AqsAAAAAADwAPAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAEDH5E8AAEDIbvnCABFAAAoHQhAAIAGxs0KAQFnCgEBkgTSAFAA5TEt AAwrMVAQIjgUMQAAAAAAAAAAswOrAAAAAAAPAQ8BAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAABAx+RPAABAyG75wgARQABAR4IQACABsT0CgEBZwoBAZIE0gBQAOUxLQAMKzFQGCI4EyMAAFBV VCAvdGVzdC5odG1sIEhUVFAvMS4xDQpBY2NlcHQtTGFuZ3VhZ2U6IGVuLXVzDQpUcmFuc2xhdGU6 IGYNCkNvbnRlbnQtTGVuZ3RoOiAwDQpVc2VyLUFnZW50OiBNaWNyb3NvZnQgRGF0YSBBY2Nlc3Mg SW50ZXJuZXQgUHVibGlzaGluZyBQcm92aWRlciBEQVYNCkhvc3Q6IG1tb2hhbg0KQ29ubmVjdGlv bjogS2VlcC1BbGl2ZQ0KQXV0aG9yaXphdGlvbjogQmFzaWMgYlRwdA0KDQrURasAAAAAAEwATAAA AAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAEDIbvnAAEDH5E8CABFAAA+oQJAAIAGQr0KAQGS CgEBZwBQBNIADCsxAOUyBlAYIV9jHgAASFRUUC8xLjAgMjAxIENyZWF0ZWQNCjxRqwAAAAAAZgFm AQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAQMhu+cAAQMfkTwIAEUAAViiAkAAgAZAowoB AZIKAQFnAFAE0gAMK0cA5TIGUBkhX8toAABDb250ZW50LUxlbmd0aDogMA0KRGF0ZTogTW9uLCAw OSBPY3QgMjAwMCAyMTowODoxNyBHTVQNClNlcnZsZXQtRW5naW5lOiBUb21jYXQgV2ViIFNlcnZl ci8zLjEgUkMxIChKU1AgMS4xOyBTZXJ2bGV0IDIuMjsgSmF2YSAxLjIuMjsgV2luZG93cyBOVCA0 LjAgeDg2OyBqYXZhLnZlbmRvcj1TdW4gTWljcm9zeXN0ZW1zIEluYy4pDQpDb250ZW50LUxhbmd1 YWdlOiBlbg0KQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluDQpTdGF0dXM6IDIwMQ0KU2VydmVyOiBt bW9oYW4NCkxvY2F0aW9uOiBodHRwOi8vbW1vaGFuL3dlY2Vyci50eHQNCg0K21GrAAAAAAA8ADwA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAx+RPAABAyG75wgARQAAKB8IQACABsTNCgEB ZwoBAZIE0gBQAOUyBgAMLHhQECDyE1cAAAAAAAAAAMRaqwAAAAAAPAA8AAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAQMfkTwAAQMhu+cIAEUAACggCEAAgAbDzQoBAWcKAQGSBNIAUADlMgYA DCx4UBEg8hNWAAAAAAAAAABVW6sAAAAAADwAPAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAA AAEDIbvnAAEDH5E8CABFAAAoowJAAIAGQNMKAQGSCgEBZwBQBNIADCx4AOUyB1AQIV8S6QAAAAAA AAAAOF6rAAAAAAA8ADwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAx+RPAABAyG75wgA RQAALCEIQACABsLJCgEBZwoBAZIE0wBQAOUxmAAAAABgAiAAKYwAAAIEBbQAAJFeqwAAAAAAPAA8 AAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAQMhu+cAAQMfkTwIAEUAACykAkAAgAY/zwoB AZIKAQFnAFAE0wAMKwIA5TGZYBIiOPw0AAACBAW0AAD4XqsAAAAAADwAPAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAEDH5E8AAEDIbvnCABFAAAoIghAAIAGwc0KAQFnCgEBkgTTAFAA5TGZ AAwrA1AQIjgT8gAAAAAAAAAAr1+rAAAAAAAQARABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAABAx+RPAABAyG75wgARQABAiMIQACABr/zCgEBZwoBAZIE0wBQAOUxmQAMKwNQGCI4sioAAEhF QUQgL3Rlc3QuaHRtbCBIVFRQLzEuMQ0KQWNjZXB0LUxhbmd1YWdlOiBlbi11cw0KVHJhbnNsYXRl OiBmDQpDb250ZW50LUxlbmd0aDogMA0KVXNlci1BZ2VudDogTWljcm9zb2Z0IERhdGEgQWNjZXNz IEludGVybmV0IFB1Ymxpc2hpbmcgUHJvdmlkZXIgREFWDQpIb3N0OiBtbW9oYW4NCkNvbm5lY3Rp b246IEtlZXAtQWxpdmUNCkF1dGhvcml6YXRpb246IEJhc2ljIGJUcHQNCg0Kgn+rAAAAAABHAEcA AAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAABAyG75wABAx+RPAgARQAAOaUCQACABj7CCgEB kgoBAWcAUATTAAwrAwDlMnNQGCFeVBQAAEhUVFAvMS4wIDIwMCBPSw0KrIOrAAAAAAAfAR8BAAAA AAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAABAyG75wABAx+RPAgARQABEaYCQACABjzqCgEBkgoB AWcAUATTAAwrFADlMnNQGSFes+AAAERhdGU6IE1vbiwgMDkgT2N0IDIwMDAgMjE6MDg6MTcgR01U DQpTZXJ2bGV0LUVuZ2luZTogVG9tY2F0IFdlYiBTZXJ2ZXIvMy4xIFJDMSAoSlNQIDEuMTsgU2Vy dmxldCAyLjI7IEphdmEgMS4yLjI7IFdpbmRvd3MgTlQgNC4wIHg4NjsgamF2YS52ZW5kb3I9U3Vu IE1pY3Jvc3lzdGVtcyBJbmMuKQ0KQ29udGVudC1MYW5ndWFnZTogZW4NCkNvbnRlbnQtVHlwZTog dGV4dC9wbGFpbg0KU3RhdHVzOiAyMDANCg0KQoSrAAAAAAA8ADwAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAABAx+RPAABAyG75wgARQAAKCQIQACABr/NCgEBZwoBAZIE0wBQAOUycwAMK/5Q ECE+ExcAAAAAAAAAABeGqwAAAAAAPAA8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQMf kTwAAQMhu+cIAEUAACglCEAAgAa+zQoBAWcKAQGSBNMAUADlMnMADCv+UBEhPhMWAAAAAAAAAABo hqsAAAAAADwAPAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAEDIbvnAAEDH5E8CABFAAAo pwJAAIAGPNMKAQGSCgEBZwBQBNMADCv+AOUydFAQIV4S9gAAAAAAAAAA ------_=_NextPart_000_01C03235.46BA7D3A-- From w3c-dist-auth-request@w3.org Mon Oct 9 17:32:14 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10199 for ; Mon, 9 Oct 2000 17:32:12 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id RAA12700; Mon, 9 Oct 2000 17:24:07 -0400 (EDT) Resent-Date: Mon, 9 Oct 2000 17:24:07 -0400 (EDT) Resent-Message-Id: <200010092124.RAA12700@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id RAA12665 for ; Mon, 9 Oct 2000 17:24:03 -0400 (EDT) Received: from neo.neographic.com ([209.143.245.222]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id RAA22883 for ; Mon, 9 Oct 2000 17:24:03 -0400 Received: from LALA.carpenter.ORG (Filenet-gw.filenet.com [198.3.8.1]) by neo.neographic.com (8.9.1a/8.8.4) with SMTP id RAA13248; Mon, 9 Oct 2000 17:23:29 -0400 (EDT) Date: Mon, 9 Oct 2000 14:25:56 -0700 Message-ID: <8120-Mon09Oct2000142556-0700-bill@carpenter.ORG> X-Mailer: 21.1 (patch 9) "Canyonlands" XEmacs Lucid (via feedmail 9-beta-13 I) wjc loop; VM 6.71 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: bill@carpenter.ORG (WJCarpenter) To: w3c-dist-auth@w3.org In-Reply-To: <936091CF9671D4118BEF00508BAC4B0C0C7DF8@KOVSJEXCHANGE> References: <936091CF9671D4118BEF00508BAC4B0C0C7DF8@KOVSJEXCHANGE> Subject: RE: webFolders PUT Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4412 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit mm> This is my Sniff file. No case problems Beats me. I notice you're responding with HTTP/1.0 instead of HTTP/1.1. -- bill@carpenter.ORG (WJCarpenter) PGP 0x91865119 38 95 1B 69 C9 C6 3D 25 73 46 32 04 69 D6 ED F3 From w3c-dist-auth-request@w3.org Thu Oct 19 11:29:58 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA12859 for ; Thu, 19 Oct 2000 11:29:57 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id LAA14315; Thu, 19 Oct 2000 11:12:03 -0400 (EDT) Resent-Date: Thu, 19 Oct 2000 11:12:03 -0400 (EDT) Resent-Message-Id: <200010191512.LAA14315@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id LAA14294 for ; Thu, 19 Oct 2000 11:12:00 -0400 (EDT) Received: from munich.ixos.de (HOST.31.95.ixos.de [149.235.31.95]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id LAA02324 for ; Thu, 19 Oct 2000 11:12:00 -0400 Received: from muc-imc.ixos.de (localhost [127.0.0.1]) by munich.ixos.de (8.9.3/8.9.3) with ESMTP id QAA24373 for ; Thu, 19 Oct 2000 16:09:10 +0100 (WET DST) Received: by muc-imc.ixos.de with Internet Mail Service (5.5.2650.21) id <4V91CDTB>; Thu, 19 Oct 2000 17:09:14 +0200 Message-ID: <077097E85A6BD3119E910800062786A90125A286@muc-mail5.ixos.de> From: Anton Schegg To: "'w3c-dist-auth@w3.org'" Date: Thu, 19 Oct 2000 16:53:39 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Subject: WebFolder does not recognize my WebDAV server Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4413 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Hello, I'm currently trying to implement a WebDAV server. Getting properties with DAV Explorer works, but Microsofts WebFolder does not recognize my implementation as a valid WebDAV server. Something is missing in my implementation of the protocol. I append a logfile and hopefully somebody can give me a hint. (I'm using Tomcat as servlet engine and http server as well). Best regards, Anton Schegg =========== LOGFILE ==================== ************************************ Establish new connection ************************************ ------------------------------------ INFO: client -> server ------------------------------------ OPTIONS / HTTP/1.1 User-Agent: Microsoft Data Access Internet Publishing Provider Cache Manager Host: muc01134:8888 Content-Length: 0 Connection: Keep-Alive ------------------------------------ INFO: server -> client ------------------------------------ HTTP/1.0 200 OK ------------------------------------ INFO: server -> client ------------------------------------ Status: 200 ------------------------------------ INFO: server -> client ------------------------------------ Allow: GET, HEAD, POST, TRACE, OPTIONS Content-Type: text/plain Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; Windows NT 5.0 x86; java.vendor=Microsoft Corp.) Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 Content-Language: en sender has closed connection: client -> server connection closed ************************************ Establish new connection ************************************ ------------------------------------ INFO: client -> server ------------------------------------ GET /_vti_inf.html HTTP/1.1 Date: Thu, 19 Oct 2000 14:59:59 GMT MIME-Version: 1.0 Accept: */* User-Agent: Mozilla/2.0 (compatible; MS FrontPage 4.0) Host: muc01134:8888 Accept: auth/sicily Content-Length: 0 Connection: Keep-Alive ------------------------------------ INFO: server -> client ------------------------------------ HTTP/1.0 404 Not Found ------------------------------------ INFO: server -> client ------------------------------------ Status: 404 ------------------------------------ INFO: server -> client ------------------------------------ Content-Type: text/html ------------------------------------ INFO: server -> client ------------------------------------ Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; Windows NT 5.0 x86; java.vendor=Microsoft Corp.) ------------------------------------ INFO: server -> client ------------------------------------ Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 ------------------------------------ INFO: server -> client ------------------------------------ Content-Language: en ------------------------------------ INFO: server -> client ------------------------------------ ------------------------------------ INFO: server -> client ------------------------------------

Error: 404

Location: /_vti_inf.html

File Not Found
/_vti_inf.html sender has closed connection: server -> client sender has closed connection: client -> server ************************************ Establish new connection ************************************ ------------------------------------ INFO: client -> server ------------------------------------ POST /_vti_bin/shtml.exe/_vti_rpc HTTP/1.1 Date: Thu, 19 Oct 2000 14:59:59 GMT MIME-Version: 1.0 User-Agent: MSFrontPage/4.0 Host: muc01134:8888 Accept: auth/sicily Content-Length: 41 Content-Type: application/x-www-form-urlencoded X-Vermeer-Content-Type: application/x-www-form-urlencoded Connection: Keep-Alive method=server+version%3a4%2e0%2e2%2e3717 ------------------------------------ INFO: server -> client ------------------------------------ HTTP/1.0 404 Not Found ------------------------------------ INFO: server -> client ------------------------------------ Status: 404 Content-Type: text/html Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; Windows NT 5.0 x86; java.vendor=Microsoft Corp.) Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 Content-Language: en

Error: 404

Location: /_vti_bin/shtml.exe/_vti_rpc

File Not Found
/_vti_bin/shtml.exe/_vti_rpc sender has closed connection: server -> client connection closed ************************************ Establish new connection ************************************ ------------------------------------ INFO: client -> server ------------------------------------ OPTIONS /DAV HTTP/1.1 Accept-Language: de, en-us;q=0.5 User-Agent: Microsoft Data Access Internet Publishing Provider DAV 1.1 Host: muc01134:8888 Content-Length: 0 Connection: Keep-Alive ------------------------------------ INFO: server -> client ------------------------------------ HTTP/1.0 200 OK ------------------------------------ INFO: server -> client ------------------------------------ Status: 200 ------------------------------------ INFO: server -> client ------------------------------------ MS-Author-Via: DAV Allow: OPTIONS, GET, HEAD, POST, DELETE, TRACE, PROPFIND, PROPPATCH, COPY, MOVE, LOCK, UNLOCK DAV: 1,2 Content-Type: text/plain Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; Windows NT 5.0 x86; java.vendor=Microsoft Corp.) Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 Content-Language: en sender has closed connection: client -> server connection closed ************************************ Establish new connection ************************************ ------------------------------------ INFO: client -> server ------------------------------------ PROPFIND /DAV HTTP/1.1 Accept-Language: de, en-us;q=0.5 Content-Type: text/xml Translate: f Content-Length: 0 Depth: 0 User-Agent: Microsoft Data Access Internet Publishing Provider DAV 1.1 Host: muc01134:8888 Connection: Keep-Alive ------------------------------------ INFO: server -> client ------------------------------------ HTTP/1.0 207 Multi-Status ------------------------------------ INFO: server -> client ------------------------------------ Status: 207 ------------------------------------ INFO: server -> client ------------------------------------ Content-Type: text/xml; charset="utf-8" ------------------------------------ INFO: server -> client ------------------------------------ Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; Windows NT 5.0 x86; java.vendor=Microsoft Corp.) Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 Content-Language: en /DAV/ 2000-08-21T09:21:17Z Wed, 13 Sep 2000 09:40:34 GMT "0-0-39bf4b92" httpd/unix-directory HTTP/1.1 200 OK sender has closed connection: server -> client sender has closed connection: client -> server From w3c-dist-auth-request@w3.org Thu Oct 19 12:47:30 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA26237 for ; Thu, 19 Oct 2000 12:47:28 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id MAA17702; Thu, 19 Oct 2000 12:32:22 -0400 (EDT) Resent-Date: Thu, 19 Oct 2000 12:32:22 -0400 (EDT) Resent-Message-Id: <200010191632.MAA17702@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id MAA17679 for ; Thu, 19 Oct 2000 12:32:18 -0400 (EDT) Received: from d06lmsgate.uk.ibm.COM (d06lmsgate.uk.ibm.com [195.212.29.1]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id MAA09832 for ; Thu, 19 Oct 2000 12:32:06 -0400 From: Tim_Ellison@uk.ibm.com Received: from d06relay02.portsmouth.uk.ibm.com (d06relay02.portsmouth.uk.ibm.com [9.166.84.148]) by d06lmsgate.uk.ibm.COM (1.0.0) with ESMTP id RAA194874; Thu, 19 Oct 2000 17:18:02 +0100 Received: from d06mta07.portsmouth.uk.ibm.com (d06mta07_cs0 [9.180.35.5]) by d06relay02.portsmouth.uk.ibm.com (8.8.8m3/NCO v4.94) with SMTP id RAA131538; Thu, 19 Oct 2000 17:31:28 +0100 Received: by d06mta07.portsmouth.uk.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 8025697D.005AC3D7 ; Thu, 19 Oct 2000 17:31:23 +0100 X-Lotus-FromDomain: IBMGB To: Anton Schegg cc: "'w3c-dist-auth@w3.org'" Message-ID: <8025697D.00598B23.00@d06mta07.portsmouth.uk.ibm.com> Date: Thu, 19 Oct 2000 17:17:14 +0100 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Re: WebFolder does not recognize my WebDAV server Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4414 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Anton, You may want to change the server to respond with HTTP/1.1 rather than HTTP/1.0 to show that it understands the 1.1 level protocol that is a prerequisite for DAV. Regards, Tim Anton Schegg on 2000-10-19 03:53:39 PM Please respond to Anton Schegg To: "'w3c-dist-auth@w3.org'" cc: Subject: WebFolder does not recognize my WebDAV server Hello, I'm currently trying to implement a WebDAV server. Getting properties with DAV Explorer works, but Microsofts WebFolder does not recognize my implementation as a valid WebDAV server. Something is missing in my implementation of the protocol. I append a logfile and hopefully somebody can give me a hint. (I'm using Tomcat as servlet engine and http server as well). Best regards, Anton Schegg =========== LOGFILE ==================== ************************************ Establish new connection ************************************ ------------------------------------ INFO: client -> server ------------------------------------ OPTIONS / HTTP/1.1 User-Agent: Microsoft Data Access Internet Publishing Provider Cache Manager Host: muc01134:8888 Content-Length: 0 Connection: Keep-Alive ------------------------------------ INFO: server -> client ------------------------------------ HTTP/1.0 200 OK ------------------------------------ INFO: server -> client ------------------------------------ Status: 200 ------------------------------------ INFO: server -> client ------------------------------------ Allow: GET, HEAD, POST, TRACE, OPTIONS Content-Type: text/plain Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; Windows NT 5.0 x86; java.vendor=Microsoft Corp.) Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 Content-Language: en sender has closed connection: client -> server connection closed ************************************ Establish new connection ************************************ ------------------------------------ INFO: client -> server ------------------------------------ GET /_vti_inf.html HTTP/1.1 Date: Thu, 19 Oct 2000 14:59:59 GMT MIME-Version: 1.0 Accept: */* User-Agent: Mozilla/2.0 (compatible; MS FrontPage 4.0) Host: muc01134:8888 Accept: auth/sicily Content-Length: 0 Connection: Keep-Alive ------------------------------------ INFO: server -> client ------------------------------------ HTTP/1.0 404 Not Found ------------------------------------ INFO: server -> client ------------------------------------ Status: 404 ------------------------------------ INFO: server -> client ------------------------------------ Content-Type: text/html ------------------------------------ INFO: server -> client ------------------------------------ Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; Windows NT 5.0 x86; java.vendor=Microsoft Corp.) ------------------------------------ INFO: server -> client ------------------------------------ Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 ------------------------------------ INFO: server -> client ------------------------------------ Content-Language: en ------------------------------------ INFO: server -> client ------------------------------------ ------------------------------------ INFO: server -> client ------------------------------------

Error: 404

Location: /_vti_inf.html

File Not Found
/_vti_inf.html sender has closed connection: server -> client sender has closed connection: client -> server ************************************ Establish new connection ************************************ ------------------------------------ INFO: client -> server ------------------------------------ POST /_vti_bin/shtml.exe/_vti_rpc HTTP/1.1 Date: Thu, 19 Oct 2000 14:59:59 GMT MIME-Version: 1.0 User-Agent: MSFrontPage/4.0 Host: muc01134:8888 Accept: auth/sicily Content-Length: 41 Content-Type: application/x-www-form-urlencoded X-Vermeer-Content-Type: application/x-www-form-urlencoded Connection: Keep-Alive method=server+version%3a4%2e0%2e2%2e3717 ------------------------------------ INFO: server -> client ------------------------------------ HTTP/1.0 404 Not Found ------------------------------------ INFO: server -> client ------------------------------------ Status: 404 Content-Type: text/html Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; Windows NT 5.0 x86; java.vendor=Microsoft Corp.) Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 Content-Language: en

Error: 404

Location: /_vti_bin/shtml.exe/_vti_rpc

File Not Found
/_vti_bin/shtml.exe/_vti_rpc sender has closed connection: server -> client connection closed ************************************ Establish new connection ************************************ ------------------------------------ INFO: client -> server ------------------------------------ OPTIONS /DAV HTTP/1.1 Accept-Language: de, en-us;q=0.5 User-Agent: Microsoft Data Access Internet Publishing Provider DAV 1.1 Host: muc01134:8888 Content-Length: 0 Connection: Keep-Alive ------------------------------------ INFO: server -> client ------------------------------------ HTTP/1.0 200 OK ------------------------------------ INFO: server -> client ------------------------------------ Status: 200 ------------------------------------ INFO: server -> client ------------------------------------ MS-Author-Via: DAV Allow: OPTIONS, GET, HEAD, POST, DELETE, TRACE, PROPFIND, PROPPATCH, COPY, MOVE, LOCK, UNLOCK DAV: 1,2 Content-Type: text/plain Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; Windows NT 5.0 x86; java.vendor=Microsoft Corp.) Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 Content-Language: en sender has closed connection: client -> server connection closed ************************************ Establish new connection ************************************ ------------------------------------ INFO: client -> server ------------------------------------ PROPFIND /DAV HTTP/1.1 Accept-Language: de, en-us;q=0.5 Content-Type: text/xml Translate: f Content-Length: 0 Depth: 0 User-Agent: Microsoft Data Access Internet Publishing Provider DAV 1.1 Host: muc01134:8888 Connection: Keep-Alive ------------------------------------ INFO: server -> client ------------------------------------ HTTP/1.0 207 Multi-Status ------------------------------------ INFO: server -> client ------------------------------------ Status: 207 ------------------------------------ INFO: server -> client ------------------------------------ Content-Type: text/xml; charset="utf-8" ------------------------------------ INFO: server -> client ------------------------------------ Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; Windows NT 5.0 x86; java.vendor=Microsoft Corp.) Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 Content-Language: en /DAV/ 2000-08-21T09:21:17Z Wed, 13 Sep 2000 09:40:34 GMT "0-0-39bf4b92" httpd/unix-directory HTTP/1.1 200 OK sender has closed connection: server -> client sender has closed connection: client -> server From w3c-dist-auth-request@w3.org Thu Oct 19 12:53:52 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA27664 for ; Thu, 19 Oct 2000 12:53:49 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id MAA17975; Thu, 19 Oct 2000 12:40:21 -0400 (EDT) Resent-Date: Thu, 19 Oct 2000 12:40:21 -0400 (EDT) Resent-Message-Id: <200010191640.MAA17975@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id MAA17955 for ; Thu, 19 Oct 2000 12:40:18 -0400 (EDT) Received: from services.cse.ucsc.edu (services.cse.ucsc.edu [128.114.48.10]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id MAA10491 for ; Thu, 19 Oct 2000 12:40:18 -0400 Received: from galileo (dhcp-63-142.cse.ucsc.edu [128.114.63.142]) by services.cse.ucsc.edu (8.9.1a/8.9.1) with SMTP id JAA11754 for ; Thu, 19 Oct 2000 09:40:16 -0700 (PDT) From: "Jim Whitehead" To: "WebDAV WG" Date: Thu, 19 Oct 2000 09:38:14 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Subject: FW: Creating a new Email message Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4415 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Accidentally caught by the spam filter. I've added dgeorgakopoulos@habama.com to the accept2 list. - Jim -----Original Message----- From: Dimitris Georgakopoulos [mailto:dgeorgakopoulos@habama.com] Sent: Wednesday, October 18, 2000 5:30 PM To: 'w3c-dist-auth@w3.org' Subject: [Moderator Action] Creating a new Email message Hello, I am kind of new to the protocol and I am trying to find out the request xml grammar that I need to submit to the WebDav Exchange 2000 server to send a new email message. Any information would be greatly appreciated From w3c-dist-auth-request@w3.org Thu Oct 19 12:55:19 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA27984 for ; Thu, 19 Oct 2000 12:55:17 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id MAA18020; Thu, 19 Oct 2000 12:42:20 -0400 (EDT) Resent-Date: Thu, 19 Oct 2000 12:42:20 -0400 (EDT) Resent-Message-Id: <200010191642.MAA18020@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id MAA18000 for ; Thu, 19 Oct 2000 12:42:17 -0400 (EDT) Received: from kovsjexchange.kovair.com (unnamed.kovair.com [63.112.189.161] (may be forged)) by tux.w3.org (8.9.3/8.9.3) with ESMTP id MAA10648 for ; Thu, 19 Oct 2000 12:42:12 -0400 Received: by KOVSJEXCHANGE with Internet Mail Service (5.5.2650.21) id <4P2YATTD>; Thu, 19 Oct 2000 09:42:12 -0700 Message-ID: <936091CF9671D4118BEF00508BAC4B0C0C7E2A@KOVSJEXCHANGE> From: Madan Mohan To: "'Anton Schegg'" , "'w3c-dist-auth@w3.org'" Date: Thu, 19 Oct 2000 09:42:11 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: WebFolder does not recognize my WebDAV server Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4416 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Hi You have to inform WebFolders that you support WedDav. Or else it will look for frontpage extensions (_vtf_inf.html). So for the OPTIONS request that is comming first you should respond by giving the headers DAV and MS-Author-Via "DAV :1.1" "MS-Author-Via: DAV" When WebFolders sees this then it will send a PROPFIND webdav request instead of the GET request that you are getting now Cheers D.Madan Mohan From w3c-dist-auth-request@w3.org Thu Oct 19 13:06:17 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00299 for ; Thu, 19 Oct 2000 13:06:16 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id MAA18383; Thu, 19 Oct 2000 12:53:27 -0400 (EDT) Resent-Date: Thu, 19 Oct 2000 12:53:27 -0400 (EDT) Resent-Message-Id: <200010191653.MAA18383@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id MAA18363 for ; Thu, 19 Oct 2000 12:53:23 -0400 (EDT) Received: from ladon.host4u.net (ladon.host4u.net [216.71.64.24]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id MAA11563 for ; Thu, 19 Oct 2000 12:53:19 -0400 Received: from Win98600 (w254.z216112214.lax-ca.dsl.cnc.net [216.112.214.254]) by ladon.host4u.net (8.8.5/8.8.5) with ESMTP id LAA04213; Thu, 19 Oct 2000 11:27:07 -0500 Message-ID: <002401c039ed$e6d7ab20$fed670d8@concentric.net> From: "John Glavin" To: "Anton Schegg" Cc: References: <077097E85A6BD3119E910800062786A90125A286@muc-mail5.ixos.de> Date: Thu, 19 Oct 2000 09:59:09 -0700 Organization: RiverFront Software MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Subject: Re: WebFolder does not recognize my WebDAV server Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4417 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit I think the problem is your Allow: you don't list MKCOL or PROPFIND so the webfolders is thinking you are not a DAV server and is switching into FrontPage Extension mode. A good way to find out what you need to return is run a packet tracer and connect with webfolders to a DAV server, like www.sharemation.com and see what they return to make webfolders think it's a DAV server. John Glavin RiverFront Software http://www.webdrive.com ----- Original Message ----- From: Anton Schegg To: Sent: Thursday, October 19, 2000 7:53 AM Subject: WebFolder does not recognize my WebDAV server > Hello, > > I'm currently trying to implement a WebDAV server. Getting properties with > DAV Explorer works, but Microsofts WebFolder does not recognize my > implementation as a valid WebDAV server. Something is missing in my > implementation of the protocol. I append a logfile and hopefully somebody > can give me a hint. (I'm using Tomcat as servlet engine and http server as > well). > > Best regards, > Anton Schegg > > =========== LOGFILE ==================== > ************************************ > Establish new connection > ************************************ > ------------------------------------ > INFO: client -> server > ------------------------------------ > OPTIONS / HTTP/1.1 > User-Agent: Microsoft Data Access Internet Publishing Provider Cache Manager > Host: muc01134:8888 > Content-Length: 0 > Connection: Keep-Alive > > ------------------------------------ > INFO: server -> client > ------------------------------------ > HTTP/1.0 200 OK > ------------------------------------ > INFO: server -> client > ------------------------------------ > Status: 200 > ------------------------------------ > INFO: server -> client > ------------------------------------ > Allow: GET, HEAD, POST, TRACE, OPTIONS > Content-Type: text/plain > Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; > Windows NT 5.0 x86; java.vendor=Microsoft Corp.) > Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 > Content-Language: en > > sender has closed connection: client -> server > connection closed > ************************************ > Establish new connection > ************************************ > ------------------------------------ > INFO: client -> server > ------------------------------------ > GET /_vti_inf.html HTTP/1.1 > Date: Thu, 19 Oct 2000 14:59:59 GMT > MIME-Version: 1.0 > Accept: */* > User-Agent: Mozilla/2.0 (compatible; MS FrontPage 4.0) > Host: muc01134:8888 > Accept: auth/sicily > Content-Length: 0 > Connection: Keep-Alive > > ------------------------------------ > INFO: server -> client > ------------------------------------ > HTTP/1.0 404 Not Found > ------------------------------------ > INFO: server -> client > ------------------------------------ > Status: 404 > ------------------------------------ > INFO: server -> client > ------------------------------------ > Content-Type: text/html > ------------------------------------ > INFO: server -> client > ------------------------------------ > Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; > Windows NT 5.0 x86; java.vendor=Microsoft Corp.) > ------------------------------------ > INFO: server -> client > ------------------------------------ > Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 > ------------------------------------ > INFO: server -> client > ------------------------------------ > Content-Language: en > ------------------------------------ > INFO: server -> client > ------------------------------------ > > ------------------------------------ > INFO: server -> client > ------------------------------------ >

Error: 404

>

Location: /_vti_inf.html

File Not Found
/_vti_inf.html > sender has closed connection: server -> client > sender has closed connection: client -> server > ************************************ > Establish new connection > ************************************ > ------------------------------------ > INFO: client -> server > ------------------------------------ > POST /_vti_bin/shtml.exe/_vti_rpc HTTP/1.1 > Date: Thu, 19 Oct 2000 14:59:59 GMT > MIME-Version: 1.0 > User-Agent: MSFrontPage/4.0 > Host: muc01134:8888 > Accept: auth/sicily > Content-Length: 41 > Content-Type: application/x-www-form-urlencoded > X-Vermeer-Content-Type: application/x-www-form-urlencoded > Connection: Keep-Alive > > method=server+version%3a4%2e0%2e2%2e3717 > > ------------------------------------ > INFO: server -> client > ------------------------------------ > HTTP/1.0 404 Not Found > ------------------------------------ > INFO: server -> client > ------------------------------------ > Status: 404 > Content-Type: text/html > Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; > Windows NT 5.0 x86; java.vendor=Microsoft Corp.) > Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 > Content-Language: en > >

Error: 404

>

Location: /_vti_bin/shtml.exe/_vti_rpc

File Not > Found
/_vti_bin/shtml.exe/_vti_rpc > sender has closed connection: server -> client > connection closed > ************************************ > Establish new connection > ************************************ > ------------------------------------ > INFO: client -> server > ------------------------------------ > OPTIONS /DAV HTTP/1.1 > Accept-Language: de, en-us;q=0.5 > User-Agent: Microsoft Data Access Internet Publishing Provider DAV 1.1 > Host: muc01134:8888 > Content-Length: 0 > Connection: Keep-Alive > > ------------------------------------ > INFO: server -> client > ------------------------------------ > HTTP/1.0 200 OK > ------------------------------------ > INFO: server -> client > ------------------------------------ > Status: 200 > ------------------------------------ > INFO: server -> client > ------------------------------------ > MS-Author-Via: DAV > Allow: OPTIONS, GET, HEAD, POST, DELETE, TRACE, PROPFIND, PROPPATCH, COPY, > MOVE, LOCK, UNLOCK > DAV: 1,2 > Content-Type: text/plain > Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; > Windows NT 5.0 x86; java.vendor=Microsoft Corp.) > Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 > Content-Language: en > > sender has closed connection: client -> server > connection closed > ************************************ > Establish new connection > ************************************ > ------------------------------------ > INFO: client -> server > ------------------------------------ > PROPFIND /DAV HTTP/1.1 > Accept-Language: de, en-us;q=0.5 > Content-Type: text/xml > Translate: f > Content-Length: 0 > Depth: 0 > User-Agent: Microsoft Data Access Internet Publishing Provider DAV 1.1 > Host: muc01134:8888 > Connection: Keep-Alive > > ------------------------------------ > INFO: server -> client > ------------------------------------ > HTTP/1.0 207 Multi-Status > ------------------------------------ > INFO: server -> client > ------------------------------------ > Status: 207 > ------------------------------------ > INFO: server -> client > ------------------------------------ > Content-Type: text/xml; charset="utf-8" > ------------------------------------ > INFO: server -> client > ------------------------------------ > Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; > Windows NT 5.0 x86; java.vendor=Microsoft Corp.) > Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 > Content-Language: en > > > > > /DAV/ > > > 2000-08-21T09:21:17Z > Wed, 13 Sep 2000 09:40:34 > GMT > "0-0-39bf4b92" > > > > > > > > > > > > > > > > > > > > > > > > httpd/unix-directory > > HTTP/1.1 200 OK > > > > sender has closed connection: server -> client > sender has closed connection: client -> server From w3c-dist-auth-request@w3.org Thu Oct 19 17:15:32 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10642 for ; Thu, 19 Oct 2000 17:15:31 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id RAA03743; Thu, 19 Oct 2000 17:03:34 -0400 (EDT) Resent-Date: Thu, 19 Oct 2000 17:03:34 -0400 (EDT) Resent-Message-Id: <200010192103.RAA03743@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id RAA03720 for ; Thu, 19 Oct 2000 17:03:30 -0400 (EDT) Received: from kurgan.lyra.org ([198.144.203.199]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id RAA05380 for ; Thu, 19 Oct 2000 17:03:11 -0400 Received: (from gstein@localhost) by kurgan.lyra.org (8.9.3/8.9.3) id OAA00754; Thu, 19 Oct 2000 14:00:29 -0700 X-Authentication-Warning: kurgan.lyra.org: gstein set sender to gstein@lyra.org using -f Date: Thu, 19 Oct 2000 14:00:29 -0700 From: Greg Stein To: Anton Schegg Cc: "'w3c-dist-auth@w3.org'" Message-ID: <20001019140029.A739@lyra.org> Mail-Followup-To: Anton Schegg , "'w3c-dist-auth@w3.org'" References: <077097E85A6BD3119E910800062786A90125A286@muc-mail5.ixos.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <077097E85A6BD3119E910800062786A90125A286@muc-mail5.ixos.de>; from anton.schegg@ixos.de on Thu, Oct 19, 2000 at 04:53:39PM +0200 X-URL: http://www.lyra.org/greg/ Subject: Re: WebFolder does not recognize my WebDAV server Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4418 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Oh, geez. What has this list come to. Three replies, and three incorrect (or close to it) answers... A1: "respond with HTTP/1.1" --> well, this is obviously not a prerequisite because we see that Web Folders *does* end up doing a PROPFIND. So it obviously doesn't mind. A2: "use 'DAV :1.1' and 'MS-Author-Via: DAV'" --> the former should be the 'DAV: 1,2' header and the latter is not required (it simply optimizes out a round trip). We also see in the log below that Anton returns those for the /DAV directory. A3: "return MKCOL and PROPFIND in the OPTIONS response" --> he is returning PROPFIND (but not MKCOL). Web Folders doesn't need the MKCOL... it already believes there is a DAV server there by the simple evidence that it issues a PROPFIND. Sigh. Yes, using HTTP/1.1 in the response is a good idea and is technically required (and it will help with connection persistence and request pipelining). But it isn't a precondition. It would be good to return MKCOL, too. I'd also suggest getting rid of that Status: header (it's useless). I believe your real problem exists in the Multistatus response. You are using the "DAV" namespace *prefix*, but have not placed the elements into the "DAV:" *namespace*. Change your outermost element to: That should hopefully do the trick. I haven't thoroughly analyzed the body of your multistatus, but a rough glance seems to show it is okay. Also, have you seen the Slide project? http://jakarta.apache.org/slide/ Or the Magi-DAV project? http://magi.endeavors.org/ Cheers, -g On Thu, Oct 19, 2000 at 04:53:39PM +0200, Anton Schegg wrote: >... > ************************************ > Establish new connection > ************************************ > ------------------------------------ > INFO: client -> server > ------------------------------------ > PROPFIND /DAV HTTP/1.1 > Accept-Language: de, en-us;q=0.5 > Content-Type: text/xml > Translate: f > Content-Length: 0 > Depth: 0 > User-Agent: Microsoft Data Access Internet Publishing Provider DAV 1.1 > Host: muc01134:8888 > Connection: Keep-Alive > > ------------------------------------ > INFO: server -> client > ------------------------------------ > HTTP/1.0 207 Multi-Status > ------------------------------------ > INFO: server -> client > ------------------------------------ > Status: 207 > ------------------------------------ > INFO: server -> client > ------------------------------------ > Content-Type: text/xml; charset="utf-8" > ------------------------------------ > INFO: server -> client > ------------------------------------ > Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; > Windows NT 5.0 x86; java.vendor=Microsoft Corp.) > Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 > Content-Language: en > > > > > /DAV/ > > > 2000-08-21T09:21:17Z > Wed, 13 Sep 2000 09:40:34 > GMT > "0-0-39bf4b92" > > > > > > > > > > > > > > > > > > > > > > > > httpd/unix-directory > > HTTP/1.1 200 OK > > > > sender has closed connection: server -> client > sender has closed connection: client -> server -- Greg Stein, http://www.lyra.org/ From w3c-dist-auth-request@w3.org Fri Oct 20 03:06:40 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA14239 for ; Fri, 20 Oct 2000 03:06:40 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id CAA16459; Fri, 20 Oct 2000 02:52:17 -0400 (EDT) Resent-Date: Fri, 20 Oct 2000 02:52:17 -0400 (EDT) Resent-Message-Id: <200010200652.CAA16459@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id CAA16439 for ; Fri, 20 Oct 2000 02:52:13 -0400 (EDT) Received: from munich.ixos.de (HOST.31.95.ixos.de [149.235.31.95]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id CAA13893 for ; Fri, 20 Oct 2000 02:52:13 -0400 Received: from muc-imc.ixos.de (localhost [127.0.0.1]) by munich.ixos.de (8.9.3/8.9.3) with ESMTP id HAA20884 for ; Fri, 20 Oct 2000 07:49:25 +0100 (WET DST) Received: by muc-imc.ixos.de with Internet Mail Service (5.5.2650.21) id <4V91CJHL>; Fri, 20 Oct 2000 08:49:40 +0200 Message-ID: <077097E85A6BD3119E910800062786A90125A289@muc-mail5.ixos.de> From: Anton Schegg To: "'w3c-dist-auth@w3.org'" Date: Fri, 20 Oct 2000 08:34:12 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: WebFolder does not recognize my WebDAV server Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4419 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Hello all, Thanks for the answers. Specifying the namespace (xmlns:D="DAV:") in the multistatus response is the solution. Confusion was caused probably through the following: I specified "http://muc01134:8888/DAV/" in WebFolder. "/DAV/" induces tomcat to invoke my own servlet (because I configured it in that way). WebFolder now tries to get a response from "http://muc01134:8888/" before finally going to try "http://muc01134:8888/DAV/". This is the reason for having some leading requests (WebFolder checks for frontpage extensions) and responses in my logfile, which are handled by the HTTP-Server itself and without invoking my servlet. Best regards, Anton Schegg -----Original Message----- From: Greg Stein [mailto:gstein@lyra.org] Sent: Thursday, October 19, 2000 11:00 PM To: Anton Schegg Cc: 'w3c-dist-auth@w3.org' Subject: Re: WebFolder does not recognize my WebDAV server Oh, geez. What has this list come to. Three replies, and three incorrect (or close to it) answers... A1: "respond with HTTP/1.1" --> well, this is obviously not a prerequisite because we see that Web Folders *does* end up doing a PROPFIND. So it obviously doesn't mind. A2: "use 'DAV :1.1' and 'MS-Author-Via: DAV'" --> the former should be the 'DAV: 1,2' header and the latter is not required (it simply optimizes out a round trip). We also see in the log below that Anton returns those for the /DAV directory. A3: "return MKCOL and PROPFIND in the OPTIONS response" --> he is returning PROPFIND (but not MKCOL). Web Folders doesn't need the MKCOL... it already believes there is a DAV server there by the simple evidence that it issues a PROPFIND. Sigh. Yes, using HTTP/1.1 in the response is a good idea and is technically required (and it will help with connection persistence and request pipelining). But it isn't a precondition. It would be good to return MKCOL, too. I'd also suggest getting rid of that Status: header (it's useless). I believe your real problem exists in the Multistatus response. You are using the "DAV" namespace *prefix*, but have not placed the elements into the "DAV:" *namespace*. Change your outermost element to: That should hopefully do the trick. I haven't thoroughly analyzed the body of your multistatus, but a rough glance seems to show it is okay. Also, have you seen the Slide project? http://jakarta.apache.org/slide/ Or the Magi-DAV project? http://magi.endeavors.org/ Cheers, -g From w3c-dist-auth-request@w3.org Fri Oct 20 19:36:57 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA07756 for ; Fri, 20 Oct 2000 19:36:57 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id TAA28674; Fri, 20 Oct 2000 19:27:02 -0400 (EDT) Resent-Date: Fri, 20 Oct 2000 19:27:02 -0400 (EDT) Resent-Message-Id: <200010202327.TAA28674@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id TAA28654 for ; Fri, 20 Oct 2000 19:26:58 -0400 (EDT) Received: from services.cse.ucsc.edu (services.cse.ucsc.edu [128.114.48.10]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id TAA07736 for ; Fri, 20 Oct 2000 19:26:58 -0400 Received: from galileo (dhcp-63-142.cse.ucsc.edu [128.114.63.142]) by services.cse.ucsc.edu (8.9.1a/8.9.1) with SMTP id QAA14408 for ; Fri, 20 Oct 2000 16:26:57 -0700 (PDT) From: "Jim Whitehead" To: "WebDAV WG" Date: Fri, 20 Oct 2000 16:24:17 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Subject: Re: WebFolder does not recognize my WebDAV server Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4420 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit Accidentally caught by the spam filter. I've added Joe's new email address to the accept2 list. - Jim -----Original Message----- From: Joe Orton [mailto:joe@light.plus.com] Sent: Thursday, October 19, 2000 2:31 PM To: 'w3c-dist-auth@w3.org' Subject: [Moderator Action] Re: WebFolder does not recognize my WebDAV server The OPTIONS response should include the headers DAV: 1 MS-Author-Via: DAV (the latter is only for best results against MS clients) As others have said, PROPFIND etc in the Allow header (don't know if MS clients check this or not). > Allow: GET, HEAD, POST, TRACE, OPTIONS > Content-Type: text/plain > Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.1.4; > Windows NT 5.0 x86; java.vendor=Microsoft Corp.) > Date: Thu, 19 Oct 2000 14:59:59 GMT+00:00 > Content-Language: en ... then, the PROPFIND response is not right. You need to use namespaces properly, e.g. first, and then replace DAV: everywhere below with D: > > > From w3c-dist-auth-request@w3.org Sat Oct 21 15:29:46 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA14581 for ; Sat, 21 Oct 2000 15:29:44 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id PAA19383; Sat, 21 Oct 2000 15:15:57 -0400 (EDT) Resent-Date: Sat, 21 Oct 2000 15:15:57 -0400 (EDT) Resent-Message-Id: <200010211915.PAA19383@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id PAA19363 for ; Sat, 21 Oct 2000 15:15:53 -0400 (EDT) Received: from smtprelay3.adelphia.net (smtprelay3.adelphia.net [64.8.25.8]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id PAA17146 for ; Sat, 21 Oct 2000 15:15:54 -0400 Received: from h2g4a1 ([24.51.141.24]) by smtprelay3.adelphia.net (Netscape Messaging Server 4.15) with SMTP id G2SO1T00.A3X for ; Sat, 21 Oct 2000 15:13:05 -0400 From: "m20bi" To: Date: Sat, 21 Oct 2000 15:16:12 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Subject: httpd.conf for RedHat 6.2 Apache 1.3.12-2 Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4421 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit I'm tearing my hair out. Would someone be so kind as to send a copy of their httpd.conf file to me so I can debug this mod_dav 1.0.2 installation. Thank you, Barbara From w3c-dist-auth-request@w3.org Tue Oct 24 17:18:46 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA13325 for ; Tue, 24 Oct 2000 17:18:43 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id RAA06700; Tue, 24 Oct 2000 17:06:24 -0400 (EDT) Resent-Date: Tue, 24 Oct 2000 17:06:24 -0400 (EDT) Resent-Message-Id: <200010242106.RAA06700@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id RAA06677 for ; Tue, 24 Oct 2000 17:06:13 -0400 (EDT) Received: from gw.atria.com (gw.atria.com [192.88.237.2]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id RAA08260 for ; Tue, 24 Oct 2000 17:05:58 -0400 Received: from 204.167.8.157 (tantalum.atria.com) by gw.atria.com id Tue, 24 Oct 2000 17:05:56 -0400 (EDT) Received: (from gclemm@localhost) by tantalum.atria.com (8.8.8+Sun/8.8.8) id RAA08708; Tue, 24 Oct 2000 17:05:24 -0400 (EDT) Date: Tue, 24 Oct 2000 17:05:24 -0400 (EDT) Message-Id: <200010242105.RAA08708@tantalum.atria.com> X-Authentication-Warning: tantalum.atria.com: gclemm set sender to geoffrey.clemm@rational.com using -f From: "Geoffrey M. Clemm" To: w3c-dist-auth@w3.org Subject: returning the lock token from a LOCK Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4422 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: In section 6.3 of 2518, it says "a lock token is returned by every successful LOCK operation in the lockdiscovery property in the response body". But then in section 8.10.1, it says "In order to indicate the lock token associated with a newly created lock, a Lock-Token response header MUST be included in the response for every successful LOCK request for a new lock." But then in the examples, no Lock-Token response header is included. This needs to be cleaned up. My personal preference is to go with section 8.10.1, unless there are servers/clients out there that depend on the section 6.3 semantics, in which case we probably should require it to appear in *both* the header and the body (gross). Cheers, Geoff From w3c-dist-auth-request@w3.org Wed Oct 25 17:42:11 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20454 for ; Wed, 25 Oct 2000 17:42:08 -0400 (EDT) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id RAA17539; Wed, 25 Oct 2000 17:29:38 -0400 (EDT) Resent-Date: Wed, 25 Oct 2000 17:29:38 -0400 (EDT) Resent-Message-Id: <200010252129.RAA17539@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id RAA17424 for ; Wed, 25 Oct 2000 17:29:33 -0400 (EDT) Received: from sioux.hosts.netdirect.net.uk (root@sioux.hosts.netdirect.net.uk [195.7.224.43]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id RAA21165 for ; Wed, 25 Oct 2000 17:29:32 -0400 Received: from ojzxmxqo (th-pm07-29.ndirect.co.uk [195.7.228.157]) by sioux.hosts.netdirect.net.uk (8.9.3/8.9.3/Debian/GNU) with SMTP id WAA06997 for ; Wed, 25 Oct 2000 22:29:26 +0100 Message-ID: <005801c03ecb$6dba8f40$0200000a@ojzxmxqo> From: "csamson" To: Date: Wed, 25 Oct 2000 22:34:59 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Subject: WebDAV ENABLED JAVA APPLET FOR RESOURCE PLANNING Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4423 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit We have developed a Java Applet that uses WebDAV to manage resources via a browser. It currently works well using IE and Netscape on Windows, but may not work on some Mac clients - we'd be interested in feedback on what does/doesn't work. The Applet is currently on the sharemation WebDAV supported site www.sharemation.com. Try it by first going to http://www.screenplan.com/eplan2.html mydocsonline has been tested, but it does not seem to support the LOCK command which is used by the Applet. Thanks to the WebDAV mailing list for providing assistance on some of the technical issues. Any WebDAV mailing list members/developers who want to use this Applet (either for testing or practical use!) please let us know - we'll provide a trial version. Regards, JC Samson --------------------------- JAVA WEBDAV APPLET FOR RESOURCE PLANNING RELEASED 24 October 2000 A Java Applet has been developed that can be used to manage shared resources using a World Wide Web browser. It uses XML (eXtensible Markup Language) to manage resource information - and the recently released WebDAV HTTP extensions to allow updating of resource information. It has uses throughout most organisations, including : *Staff allocation on projects/tasks *Room booking *Desk or office booking *Equipment booking *Car parking space booking Many organisations still rely on hand-written charts or paper notebooks to keep track of vital resources such as meeting rooms or car parking spaces. The Java Applet allows staff to view and update resource allocation from their desk or even remotely, using a Java-compatible device. From w3c-dist-auth-request@w3.org Mon Oct 30 19:35:33 2000 Received: from www19.w3.org (www19.w3.org [18.29.0.19]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA04639 for ; Mon, 30 Oct 2000 19:35:33 -0500 (EST) Received: (from daemon@localhost) by www19.w3.org (8.9.0/8.9.0) id TAA26782; Mon, 30 Oct 2000 19:23:22 -0500 (EST) Resent-Date: Mon, 30 Oct 2000 19:23:22 -0500 (EST) Resent-Message-Id: <200010310023.TAA26782@www19.w3.org> Received: from tux.w3.org (tux.w3.org [18.29.0.27]) by www19.w3.org (8.9.0/8.9.0) with ESMTP id TAA26759 for ; Mon, 30 Oct 2000 19:23:18 -0500 (EST) Received: from services.cse.ucsc.edu (services.cse.ucsc.edu [128.114.48.10]) by tux.w3.org (8.9.3/8.9.3) with ESMTP id TAA25365 for ; Mon, 30 Oct 2000 19:23:18 -0500 Received: from galileo (dhcp-63-142.cse.ucsc.edu [128.114.63.142]) by services.cse.ucsc.edu (8.9.1a/8.9.1) with SMTP id QAA12264 for ; Mon, 30 Oct 2000 16:23:16 -0800 (PST) From: "Jim Whitehead" To: "WebDAV WG" Date: Mon, 30 Oct 2000 16:20:59 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Subject: WebDAV at San Diego IETF Resent-From: w3c-dist-auth@w3.org X-Mailing-List: archive/latest/4424 X-Loop: w3c-dist-auth@w3.org Sender: w3c-dist-auth-request@w3.org Resent-Sender: w3c-dist-auth-request@w3.org Precedence: list List-Id: List-Help: List-Unsubscribe: Content-Transfer-Encoding: 7bit The WebDAV working group is scheduled to hold a meeting at the San Diego IETF meeting, IETF-49. The San Diego IETF is scheduled for December 10-15, 2000. At present, WebDAV WG will be meeting from 3:30-5:30PM, on Wednesday, December 13. Note that this time is subject to change. At present, my plan is to dedicate the meeting to discussion of the Access Control Protocol, in hopes that any existing issues can be resolved, and the spec. can be sent to working group last call soon after this meeting. Details on how to register for IETF-49, along with hotel information, can be found at: http://www.ietf.org/meetings/IETF-49.html - Jim