RE: Problem with Adobe GoLive 5.0's parsing of PROPFIND

OK,

here we go. This is a response to a PROPFIND with depth 1 on a collection
resource:

<multistatus xmlns="DAV:"
xmlns:dt="urn:uuid:c2f41010-65b3-11d1-a29f-00aa00c14882/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <response>
    <href>/wcm/webdav/test/</href>
    <propstat>
      <prop>
        <supportedlock>
          <lockentry>
            <lockscope>
              <exclusive/>
            </lockscope>
            <locktype>
              <write/>
            </locktype>
          </lockentry>
        </supportedlock>
        <getlastmodified dt:dt="dateTime.rfc1123">Mon, 21 May 2001 09:50:49
GMT</getlastmodified>
        <lockdiscovery/>
        <resourcetype>
          <collection/>
        </resourcetype>
        <creationdate
dt:dt="dateTime.tz">2001-05-21T09:50:49Z</creationdate>
        <displayname>/</displayname>
        <orderingtype>
          <unordered/>
        </orderingtype>
        <getetag>"-18707824559904386492400"</getetag>
      </prop>
      <status>HTTP/1.1 200 OK</status>
    </propstat>
  </response>
  <response>
    <href>/wcm/webdav/test/ANSI.TXT</href>
    <propstat>
      <prop>
        <supportedlock>
          <lockentry>
            <lockscope>
              <exclusive/>
            </lockscope>
            <locktype>
              <write/>
            </locktype>
          </lockentry>
        </supportedlock>
        <getlastmodified dt:dt="dateTime.rfc1123">Fri, 18 May 2001 17:39:34
GMT</getlastmodified>
        <lockdiscovery/>
        <resourcetype/>
        <getcontentlength>29</getcontentlength>
        <creationdate
dt:dt="dateTime.tz">2001-05-18T17:39:34Z</creationdate>
        <displayname>ANSI.TXT</displayname>
        <getcontenttype>text/plain</getcontenttype>
        <getetag>"983715736990207574624990438302415"</getetag>
        <julian>
          <href>mailto:fax@greenbytes.de</href>
        </julian>
      </prop>
      <status>HTTP/1.1 200 OK</status>
    </propstat>
  </response>
</multistatus>


> -----Original Message-----
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Hartmut Warncke
> Sent: Monday, May 21, 2001 11:34 AM
> To: Julian Reschke
> Cc: w3c-dist-auth@w3.org
> Subject: Re: Problem with Adobe GoLive 5.0's parsing of PROPFIND
>
>
>
> Julian,
>
> could you send the significant part of your server response so
> that we are able
> to check what is going on?
>
> Best, Hartmut
>
>
> Julian Reschke wrote:
>
> > Hi,
> >
> > we are currently doing interoperability testing with our WebDAV server.
> >
> > We found that GoLive 5.0 (evaluation version) seems to do a
> validation of
> > PROPFIND responses based on an internal DTD (or something similar).
> >
> > For properties in the DAV: namespace that contain a child element "href"
> > (something completely legal), it reports:
> >
> > "DAV-server response is not correct according to the
> DAV-Protocol, you will
> > probably lose some important information", with the details
> "Predecessor of
> > a Href-Tag must be a Response-, Locktoken, or Owner-Tag."
> >
> > Do we have Adobe employees reading this list?
> >
> > Julian
>

Received on Monday, 21 May 2001 05:57:06 UTC