does anyone have a real answer to the SignatureDoesNotMatch problem with storages?
I have searched and I see that everyone has problems with the same "SignatureDoesNotMatch", in different libraries and different languages.
I've searched and I see that everyone has the same problem with "SignatureDoesNotMatch", in several libraries and several languages they only give answers depending on the library, does anyone know what is the real problem to solve in different libraries and different languages and not have to open a post for each one.
I asked for support and even they don't know what the problem is, they sent me to the community, because it seems a complex problem.
I uploaded my static files with django-storage and when I request them with the same django-storage some of them arrive with a 403 and SignatureDoesNotMatch.
I upload files with s3cmd with some keys and when I request them with django-storege and the same keys the problem is worse.
DEFAULT_FILE_STORAGE = 'citoplus.custom_storage.MediaStorage'.
STATICFILES_STORAGE = 'citoplus.custom_storage.StaticStorage'.
LINODE_BUCKET = 'citoplusrecmedia'
LINODE_BUCKET_REGION = "us-east-1"
LINODE_BUCKET_ACCESS_KEY = "--"
LINODE_BUCKET_SECRET_KEY = "--"
AWS_S3_ENDPOINT_URL = f'https://{LINODE_BUCKET_REGION}.linodeobjects.com'
AWS_ACCESS_KEY_ID = LINODE_BUCKET_ACCESS_KEY
AWS_SECRET_ACCESS_KEY = LINODE_BUCKET_SECRET_KEY
AWS_S3_REGION_NAME = LINODE_BUCKET_REGION
AWS_S3_USE_SSL = True
AWS_S3_ENCRYPTION = True
1 Reply
your problem is special characters, simply ":" is my case.
SignatureDoesNotMatch: it takes the complete name of the file and signs it with the other keys, when taking things like these ":" simply the signature breaks like paper, and it will not work.
if you are migrating and have file names with special characters, think about it.