Three upload modes are currently supported: Normal upload, callback upload, and notification upload.

Normal Upload

All the upload return results are controlled by the cloud storage platform to standardize unification.

Callback Upload

Format customization of the information returned to the client is performed after a file is uploaded.

Callback upload (POST method): The callbackUrl parameter of the Upload Policy Data needs to be enabled, and the callbackBody parameter is optional (but recommended).

To ensure security, cloud storage platform will add the Authorization information to the request header when calling back the upload interface. Enterprise web systems can block illegal callback requests by verifying the validity of such information.

Retry Policy: Cloud storage platform is equipped with a callback request retry mechanism to ensure that callback requests can notify normally.

Notification Upload

When uploading a file, the user submits file processing instructions (including operations such as video transcoding, image watermark, and image scaling, etc.) to ask the cloud storage platform to process the uploaded file. Since these processing operations are typically quite time-consuming,
the cloud storage platform employs an asynchronous processing strategy to avoid an impact on the experience at the client. As processing procedures are executed asynchronously, the company’s web service system is notified of the result through the asynchronous notification method upon completion of processing. The company’s web system in turn interacts with the client to complete the entire processing and notification process.

Notification upload (POST method): The persistentOps parameter and persistentNotifyUrl parameter in the [Upload Policy Data]

Retry Policy: The platform will enable the retry mechanism upon failure of notification callback performed using the URL address in persistentNotifyUrl and retry 8 times by default.