Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-30154

WebDAV-Repository fails on some WebDAV-Server

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 2.0.6, 2.1.3
    • 2.0.5, 2.1.2, 2.2
    • Repositories
    • MOODLE_20_STABLE, MOODLE_21_STABLE, MOODLE_22_STABLE
    • MOODLE_20_STABLE, MOODLE_21_STABLE
    • MDL-30154_master_wip
    • Hide

      You need a free account on mydrive.ch.

      1. create a webdav-repository instance to mydrive with
        • WebDAV type: http,
        • WebDAV server: webdav.mydrive.ch
        • WebDAV path: /
        • Authentication: WebDAV basic auth
        • WebDAV server port: 80
      2. create a ressource file and connect to the repository. Folder and files should be shown and can be loaded into the file api.
      Show
      You need a free account on mydrive.ch. create a webdav-repository instance to mydrive with WebDAV type: http, WebDAV server: webdav.mydrive.ch WebDAV path: / Authentication: WebDAV basic auth WebDAV server port: 80 create a ressource file and connect to the repository. Folder and files should be shown and can be loaded into the file api.

      On some WebDAV-Server like MyDrive.ch the functions get_respond() and ls() in lib/webdavlib.php do not work properly.
      One problem is the content-type in ls(). At MyDrive.ch it is application/xml and not text/xml.
      Next problem is the max_chunk_size in get_respond(). It seams the server from MyDrive does allow only a lower size than the defined max_chunk_size of 8192. So not the full chunk is loaded and the file is cropped.
      In the file repository/webdav/lib.php the directory listing fails on MyDrive.ch.

            dongsheng Dongsheng Cai
            grabs Andreas Grabs
            Aparup Banerjee Aparup Banerjee
            Rajesh Taneja Rajesh Taneja
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.