In the docs we have a tutorial for uploading assets via rest. This approach has a few problems.

• It takes multiple calls to upload a single asset.
• It's hard to calculate the size of the asset. If you don't send the size in the request (missing from the tutorial DOCU-2430) then using the asset becomes a problem. Size is required and it would be better if it would be calculated on the server like we do with the UI upload.
• We made changes to our rest modules to restrict the use of certain characters in a node name. See MGNLREST-343 which causes MGNLREST-359. Since Magnolia 6.2.16 and rest 2.2.11 it's not possible to PUT a "jcr:content" node to store the binary data.

One solution is we provide the endpoint so that the upload can be made in one call, it can calculate the size and create the subnode. All this would make uploading assets via rest easier for the users.