Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Does order of image params matter?

See original GitHub issue

We get the following successes/failures in rendering cloudinary images in our env and I don’t understand why they should/shouldn’t work:

const imgUrl = `http://res.cloudinary.com/${account}/image/upload/h_39,q_auto,w_33/v1/${image_path}` // FAIL
const imgUrl = `http://res.cloudinary.com/${account}/image/upload/h_38,q_auto,w_33/v1/${image_path}` // FAIL
const imgUrl = `http://res.cloudinary.com/${account}/image/upload/h_37,q_auto,w_33/v1/${image_path}` // OK
const imgUrl = `http://res.cloudinary.com/${account}/image/upload/q_auto,h_39,w_33/v1/${image_path}` // OK
const imgUrl = `http://res.cloudinary.com/${account}/image/upload/h_39,w_33,q_auto/v1/${image_path}` // OK
const imgUrl = `http://res.cloudinary.com/${account}/image/upload/f_auto,h_39,q_auto,w_33/v1/${image_path}` // OK

Does order of image params matter? Am I missing something in how width,height, and quality affect one another?

Issue Analytics

State:
Created 5 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

yakirpcommented, Dec 17, 2018

So I checked this internally, and we think that there is an issue on our end about that. Using such URLs (with the “_”) should not work, you must always use the v1.

I will keep you posted, meanwhile please deliver your images only with v1.

Cheers

0reactions

roeebacommented, Feb 17, 2020

Closing this issue due to the time elapsed. Please feel free to either re-open the issue, contact our support at http://support.cloudinary.com or create a new ticket if you have any additional issues.