OK, this has been fixed both in CVS HEAD as well as in the 2.1 release
branch. Now the owner will only be wrapped inside CDATA if really
necessary. E.g. owner "<huhu" would still be wrapped.

Oliver 


On Thu, 2 Dec 2004 16:16:52 +0100, Oliver Zeigermann
<[EMAIL PROTECTED]> wrote:
> Isn't this the same problem as described in
> 
> http://issues.apache.org/bugzilla/show_bug.cgi?id=32436
> 
> However, Gregory says, it has nothing to do with the CDATA block.
> 
> I think putting the name in a CDATA block really is a bug at least as
> it contains the namespcace reference.
> 
> I will thing of a solution...
> 
> Oliver
> 
> 
> 
> On Thu, 2 Dec 2004 14:08:49 +0000, Carlos Valiente
> <[EMAIL PROTECTED]> wrote:
> > Hi! I'm having some troubles PUTting files Slide (2.0) with
> > Dreamweaver (MX 2004) via WebDAV.
> >
> > Before PUTting a file, DreamWeaver tires to LOCK it, and the issues a
> > PROPFIND request to retrieve the lock token. It then includes the lock
> > token in the If: header in the following PUT request.
> >
> > The problem seems to be Slide's response to the PROPFIND command
> > issued by DreamWeaver in order to discover the locks for a given file.
> > Slide returns:
> >
> > ...
> > <D:owner>
> >    <![CDATA[
> >       <D:href xmlns:D="DAV:">XXXX</D:href>]]>
> >    </D:owner>
> > ...
> >
> > ,whereas Apache mod_dav returns:
> >
> > ...
> > <ns0:owner xmlns:ns0="DAV:">
> >   <ns0:href>XXX</ns0:href>
> > </ns0:owner>
> >
> > DreamWeaver can cope perfectly with mod_dav's response, but not with 
> > Slide's.
> >
> > My question is: Is Slide's approach correct (returning the lock HREF
> > as CDATA instead of as a proper XML tag)?
> >
> > Many thanks,
> >
> > C
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to