I just tried to upload a file with the name Screencast from 2024-02-10 13-37-07.webm via Sharesome, which Firefox correctly encoded as 240210-1237-Screencast%20from%202024-02-10%2013-37-07.webm. However, Liquor Cabinet wasn't able to PUT that into Garage, encountering a 403 status during the requests (resulting in a 500 for the RS client). However, when removing the spaces from the filename, the upload works.
(It's possible that this isn't a Liquor Cabinet issue, but a Garage one, so we might want to try it with a different S3 back-end first.)
I just tried to upload a file with the name `Screencast from 2024-02-10 13-37-07.webm` via Sharesome, which Firefox correctly encoded as `240210-1237-Screencast%20from%202024-02-10%2013-37-07.webm`. However, Liquor Cabinet wasn't able to PUT that into Garage, encountering a 403 status during the requests (resulting in a 500 for the RS client). However, when removing the spaces from the filename, the upload works.
(It's possible that this isn't a Liquor Cabinet issue, but a Garage one, so we might want to try it with a different S3 back-end first.)
raucao
added the bug label 2024-02-10 12:50:50 +00:00
raucao
changed title from Invalid PUT signature for certain filenames to PUT signature not accepted by Garage for certain filenames2024-02-10 12:51:13 +00:00
raucao
changed title from PUT signature not accepted by Garage for certain filenames to PUT signature invalid for certain filenames2024-03-04 13:49:23 +00:00
Confirmed to be a Liquor Cabinet issue, since it's also happening locally, with Minio and without going through a reverse proxy (i.e. completely different back-end, and connecting directly to LC).
Confirmed to be a Liquor Cabinet issue, since it's also happening locally, with Minio and without going through a reverse proxy (i.e. completely different back-end, and connecting directly to LC).
raucao
self-assigned this 2024-03-04 14:56:49 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I just tried to upload a file with the name
Screencast from 2024-02-10 13-37-07.webmvia Sharesome, which Firefox correctly encoded as240210-1237-Screencast%20from%202024-02-10%2013-37-07.webm. However, Liquor Cabinet wasn't able to PUT that into Garage, encountering a 403 status during the requests (resulting in a 500 for the RS client). However, when removing the spaces from the filename, the upload works.(It's possible that this isn't a Liquor Cabinet issue, but a Garage one, so we might want to try it with a different S3 back-end first.)
Invalid PUT signature for certain filenamesto PUT signature not accepted by Garage for certain filenamesPUT signature not accepted by Garage for certain filenamesto PUT signature invalid for certain filenamesConfirmed to be a Liquor Cabinet issue, since it's also happening locally, with Minio and without going through a reverse proxy (i.e. completely different back-end, and connecting directly to LC).