Introduction
Since NXP-29978, there is a new HTTP header that is very useful for our usage of the FileManager in the Direct Transfer feature. Its name is Idempotency-Key and its value should be a uniq ID.
As stated in TL-368, this will prevent unwanted duplicates creation and enforce upload resiliency.
Scope
- Add the new HTTP header for those requests:
- NuxeoDrive.CreateFile (sync)
NuxeoDrive.UpdateFile (sync)NuxeoDrive.AttachBlob (Direct Edit, but rarely used as it is only for Note s)Blob.AttachOnDocument (Direct Edit)- FileManager.Import (Direct Transfer)
FileManager.CreateFolder (Direct Transfer)
- Store the value in the database.
- Add logic to handle calls made when a previous one is still running (the server will return a 409 conflict error).
- Add tests.
- depends on
-
NXP-29978 Add Idempotency Key support to RequestController
- Resolved
-
NXP-30081 Add Idempotency Key support to RequestController (10.10)
- Resolved
-
NXPY-199 Add support for idempotent calls
- Resolved
- is related to
-
NXDRIVE-2065 [Direct Transfer] Leverage the FileManager
- Resolved
-
NXDRIVE-2704 Force usage of idempotent requests for large files
- Resolved
- Is referenced in