RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/FineUploader/fine-uploader/issues/1755 below:

Allow custom fields to be added to resume key · Issue #1755 · FineUploader/fine-uploader · GitHub

This repository was archived by the owner on Nov 20, 2018. It is now read-only.

Allow custom fields to be added to resume key #1755

Description Type of issue

Bug report
Feature request
Support request

Uploader type

Traditional
S3
Azure

Bug Report Fine Uploader version

5.14.0

Browsers where the bug is reproducible

any

Operating systems where the bug is reproducible

any

Exact steps required to reproduce the issue

Upload part of a large file to S3 with metadata: {user: 123, project: "xyz"}
Refresh page
Select same file to upload, but with different meta data: {user: 456, project: "abc"} (actually, I don't think this is possible, but a different file would be given this metadata)
File upload continues from where it was interrupted
When file is complete, metadata is as per original upload

Detailed explanation of the problem

Resumable uploads are saved to localStorage with fileName, size, uuid, modifiedDate etc, but metadata is not included. If a different user logs in to our app, or the same user switches to a different project and resumes the upload then when complete, the file will belong to the original user/project.

The code that parses the resume data from localStorage should compare the metadata, or onResume should provide some way for the application to compare the metadata (request.params).

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4