Eric Vanular
Eric Vanular
That's fair, I appreciate all of your work on this ecosystem. Just trying to understand whether I should wait or look for an alternative option in the meantime
Furthermore, I can see that the Etag header was successfully returned from the presigned PUT call upon successful upload
I'm experiencing the same missing ETag error in @uppy/aws-s3: 4.2.3 when uploading to Backblaze B2 through the S3 compatible API even with the CORS settings on the bucket exposing ETag...