hpbad.blogg.se

Which cloud storage system are you using? (eg Google Drive) Run the command 'rclone version' and share the full output of the command. Regardless of the "correctness" of the X-Amz-Meta-Content-Disposition values we may have, we have to go along with what we have stored because we simply cannot change tens of thousands of objects. I think when using the S3 protocol, setting Content-Disposition on PUT (creating an object) will give the advantage of having that very same "filename=" available automaticall when a GET is requested, but I am not 100% sure of that. Status code: 400, request id: 5394e15f7ac106ae, host id: aMLNlZWTDY7xkDmJWM9k5SjTpZipmvjhN Which will cause this error from the B2 backend: 8 20:33:16 ERROR : ddcce9dc0f5d4ab2a7e0ab2900b01dca: Failed to copy: InvalidRequest: invalid b2-content-disposition: hit end of string while looking for closing quote starting from 21 X-Amz-Meta-Content-Disposition : attachment filename="3 =?utf-8?q?Interaci=C3=B3n=2Epdf=22?=

This is causing problems for us since we have values like this one:

It turns out that when that metadata attribute is set, rclone will set the Content-Disposition header with the value of "X-Amz-Meta-Content-Disposition". Among all the metadata attributes we are storing with the objects, there is the X-Amz-Meta-Content-Disposition one. We are trying to upload a lot of objects from a minio instance to Backblaze B2, including the metadata. What is the problem you are having with rclone?