W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2001

Re: rfc2518 issue: DEFER_LOCK_NULL_RESOURCES_IN_SPEC

From: Ilya Kirnos <ilya.kirnos@oracle.com>
Date: Wed, 01 Aug 2001 20:20:47 -0700
Message-ID: <3B68C70F.4D41C60F@oracle.com>
To: Julian Reschke <julian.reschke@gmx.de>
CC: w3c-dist-auth@w3.org
     Inspection of OPTIONS and PROPFIND responses showed:

     1) Oracle IFS only supports DAV class 1, and doesn't return an ALLOW
     header
     on OPTIONS,


That's correct, iFS DAV does not support locking in its current version.

     2) <getetag> is "getetag_blah" for all resources,


Yes, that's a known hole.  We're looking at cache interaction for our next
release, this will fall under that.

     3) It tries to return <getlastmodified> in RFC format, but uses it's
     locale
     for formatting, which obviously will not produce an RNC formatted
     date when
     your language isn't english,

Tell me more about the problem?  Where are we using the locale?

     4) It tries to return <creationdate> in RFC format (and fails in the
     same
     way), while this should be in ISO8601 format,


Does the spec say it has to be ISO8601?  I remember that Web Folders didn't
seem to like that, so we put in a hack at the last minute to make it display
dates correctly.

     5) <getcontentlanguage> (when not "unknown") is set to language
     strings like
     "ENGLISH" (which I think is incorrect according to section 14.13 of
     [RFC2068])


Yep, that's a bug.  Will fix it in our next release.

Let me know if you found any other issues.

Thanks.

-ilya


Julian Reschke wrote:

> > From: w3c-dist-auth-request@w3.org
> > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Ilya Kirnos
> > Sent: Tuesday, July 31, 2001 3:59 AM
> > To: w3c-dist-auth@w3.org
> > Subject: RE: rfc2518 issue: DEFER_LOCK_NULL_RESOURCES_IN_SPEC
> >
> >
> > > This would be fine with me as well.  It basically says that if a LOCK
> > > is applied to an unmapped URI, the LOCK is automatically preceded with
> >
> > > a PUT with a zero-length body.  As Stefan and Lisa say, having a
> > > zero length resource remain when the LOCK is removed will not cause
> > > a problem with existing clients, and clients that care about IIS
> > already
> > > cannot expect to be able to apply MKCOL to a "lock null" resource.
> >
> > > If we didn't already have clients that expected a LOCK on an unmapped
> > > URI to succeed, I'd prefer to just say that the LOCK just returns 404
> > > on an unmapped URI, but I can live with this compromise proposal.
> >
> > I agree: my first choice would  be for abandoning the concept of a null
> > lock, but if people feel strongly they should be kept, the semantics
> > should be changed to allow the server to create an actual file to track
> > the lock.
> >
> > Among other things, this allows other protocols to have at least a shot
> > at playing nice with DAV locks.  This point (interoperability with other
> > protocols) has been brought up a couple of times in this discussion
> > already, and is an important consideration for the server I'm working on
> > (Oracle iFS), and I suspect for others as well.  It can't just be
> > ignored.
>
> Hi.
>
> If you happen to work on Oracle IFS, would it be possible to give us some
> feedback on the WebDAV compliance issues listed in
>
> <http://lists.w3.org/Archives/Public/w3c-dist-auth/2001AprJun/0253.html>
>
> ?
>
> Thanks,
>
> Julian
Received on Wednesday, 1 August 2001 23:19:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:56 GMT