-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
transformation name with spaces causes 400 error #42
Comments
Not just transformation name, public ids as well. I had a public_id that ended in a slash and it threw the same errors. Needed to urllib.quote(public_id, '') before sending it. Also public_id (and transformations also) have unicode issues so the full line to fix a public_id is:
EXCEPT fetch urls have public ids that you don't escape. |
Hi @oppianmatt I see that the last response is from a while back. Are you still experiencing the issue? |
@idobarnoam we're experiencing the issue, it's really painful!
This produces a URL like; That causes a 400 error,
The file in S3 is named |
Soooo this might not be a problem with escaping the spaces, it's a problem with the There's a few symbols that aren't valid and if it's not a valid public_id it won't auto-upload from the source bucket. I'll go via a support ticket instead as it's not really pycloudinary's problem. https://support.cloudinary.com/hc/en-us/articles/115001317409--Legal-naming-conventions FYI We get a little closer double escaping, eg The other non allowed chars are: |
Making a call to get transformations, some of them come back with spaces in the name like this:
Now trying to use that (ignoring issue #41 for now), generates a 400 server error:
The fix it seems is to renencode the name using url encoding:
The text was updated successfully, but these errors were encountered: