[Cyberduck-trac] [Cyberduck] #6577: Webdav regression between 4.0.2 and 4.1.x / 4.2.x

Cyberduck trac at trac.cyberduck.ch
Thu Mar 8 11:43:35 CET 2012


#6577: Webdav regression between 4.0.2 and 4.1.x / 4.2.x
-------------------------------------+------------------------------
 Reporter:  llange                   |         Owner:  dkocher
     Type:  defect                   |        Status:  closed
 Priority:  high                     |     Milestone:
Component:  webdav                   |       Version:  Nightly Build
 Severity:  normal                   |    Resolution:  thirdparty
 Keywords:  sharepoint space webdav  |  Architecture:  Intel
 Platform:  Mac OS X 10.6            |
-------------------------------------+------------------------------

Comment (by dkocher):

 Replying to [comment:5 llange]:
 > Sorry, duplicate post, I posted in #6094 also...
 >
 > The response is :
 > {{{
 >
 <D:response><D:href>https://XXXXXXXXXXXXX.sharepoint.emea.microsoftonline.com/XXXXX/Documents
 comptables</D:href><D:propstat><D:prop><D:displayname>Documents
 comptables</D:displayname><D:lockdiscovery/><D:supportedlock/><D:isFolder>t</D:isFolder><D:iscollection>1</D:iscollection><D:ishidden>0</D:ishidden><D:getcontenttype>application
 /octet-
 stream</D:getcontenttype><D:getcontentlength>0</D:getcontentlength><D:resourcetype><D:collection/></D:resourcetype><Repl
 :authoritative-directory>t</Repl:authoritative-
 directory><D:getlastmodified>2012-03-07T20:57:03Z</D:getlastmodified><D:creationdate>2012-03-05T14:48:59Z</D:creationdate><Repl
 :repl-uid>rid:{93D90163-CECA-41E6-A705-EF69781A4EB9}</Repl:repl-
 uid><Repl:resourcetag>rt:93D90163-CECA-
 41E6-A705-EF69781A4EB9 at 00000000000</Repl:resourcetag><D:getetag>"{93D90163
 -CECA-41E6-A705-EF69781A4EB9},0"</D:getetag></D:prop>
 > <D:status>HTTP/1.1 200 OK</D:status>
 > </D:propstat>
 > </D:response>
 > }}}
 >
 > I understand that you suggest spaces to be encoded as %20, as in
 http://www.ietf.org/rfc/rfc1738.txt , right ?
 >
 > Would you accept a patch with a (possibly hidden) configuration option
 to implement a workaround for this very specific issue ?
 > I'm not happy with the situation and the fact that some vendors do not
 respect the standards, but let's face it, it's far easier (and quicker)
 for me to patch this than 1) to have the vendor provide a fix for this
 issue on its product and all impact products (browsers, operating systems,
 third-party components) and 2) have this propagated to the shared folder
 than I want to access.
 >
 > Regards,
 >
 > Ludovic.

 You could provide a patch for [http://code.google.com/p/sardine/ sardine]
 which we make use of.

-- 
Ticket URL: <http://trac.cyberduck.ch/ticket/6577#comment:6>
Cyberduck <http://cyberduck.ch>
Open source FTP, SFTP, WebDAV, Cloud Files, Google Docs & Amazon S3 Browser for Mac & Windows.


More information about the Cyberduck-trac mailing list