+ Reply to Thread
Results 1 to 1 of 1

Thread: API 2.1-23 (Release Date: 2013-08-05) "API v. 2.1"

  1. #1

    API 2.1-23 (Release Date: 2013-08-05) "API v. 2.1"

    description
    This release focuses on a major improvement in file-encoding support. Since HiDrive users are able to upload files in any encoding, whereas JSON does only support UTF-X, previous API versions experienced some difficulty with path-based requests (e.g. GET /2.0/dir...). The update resolves those issues by returning every path- and file-name in URL-encoded format. Since this changes the documented behavior in an incompatible manner, the version number is updated to 2.1.

    The changes are only accessible via new /2.1/... endpoints. Previously existing endpoints are part of 2.1.
    An update to 2.1 endpoints is highly suggested. However, /2.0/... endpoints will be kept up for transition until further notice.


    New Version 2.1 - Endpoints /2.1/...
    Type Endpoint Description
    Improvement * /2.1/* File and path names in successful (JSON) responses are URL-encoded.
    The following bytes are encoded: the
    %-character and all bytes from 0x00 to 0x20 and 0x7F to 0xFF. Example:
    Code:
    HTTP/1.1 200 OK
    X-API-Version: 2.1-23 (#b444795)
    Content-Type: application/json
    Content-Length: 57
    
    {
      "path": "root/public/%DCbergr%F6%DFentr%E4ger.txt"  
    }

    Note * /2.1/* File and path names, that are embedded in (JSON) error responses are UTF-8-encoded as far as possible, non-UTF-8 characters are replaced by the Unicode "Replacement Character" 0xfffd (http://www.fileformat.info/info/unic...fffd/index.htm).
    Last edited by Val; 2013-10-31 at 01:37 PM.

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may edit your posts
  •