When working with long image urls, I get a 502 error

GH Creative Development

October 27, 2021 11:53

Hi support,

For one of our clients we are creating creatives with product images in them. Because the images are jpg's and we need transparent png images (because we have a colored background) we are using your amazing tool to fix this. 
But we run into a problem. 

The images that we use are by an encoded image url. 
Some of these urls are longer than the other. 
When the url gets too long, we don't see an image anymore, but get a 502 bad gateway error. 

 

Here is an example that works: 

https://image.lemonpi.io/img/https://res.cloudinary.com/ghg/image/fetch/f_png/e_make_transparent:3/https://image.lemonpi.io/a/260/decode/aHR0cHM6Ly9pa2VhLmFrYW1haXplZC5uZXQvbmwvbmwvaW1hZ2VzL3Byb2R1Y3RzL3NvcnZhbGxlbi1ob2VrYmFuay0zLXppdHMtbWV0LW9wZW4tZWluZC1saW5rcy1sZWpkZS1ncmlqcy16d2FydF9fMDc0Nzc0MF9wZTc0NDcxMV9zNC5qcGc=

 

But here is one that does not work (so you see a json file with an error)

https://image.lemonpi.io/img/https://res.cloudinary.com/ghg/image/fetch/f_png/e_make_transparent:3/https://image.lemonpi.io/a/260/decode/aHR0cHM6Ly9nZngucHJvZHVjdHN1cC5pby9pbWcvc2l0ZS80NTMzMjYvZGF0YS9MWTVCRG9Jd0VFWHZNbXNLSklDbXZZb1lNdUFJMVpZMm5XSU5oTHVMMGNYUGU4bmJfQTA0REtCZ2l0R3phb3UyU0NubC1rbVlEODYyeFd4LTB4Wkg0cmJ3d2QyV0lSNzIwdGFRbUJ5eHFNU3FJN05COUwyd0ZNVXdvV1lTWmg0RjQ1c3NCaFJyd2hCN2cwdnF1bExXOGxSWG5hZXpsTElxTzI3eWh4OGhnN3VKb0M0YkJBSzF3ZmZaN0dZNlFnTFZsR1VHMDU4ZVZBd0w3ZnQxX3dBLnBuZw==

Since this is a very long product feed and it belongs to the client, I don't have any influence on how the feed setup is. 
Is there a way to fix is? How can I make the urls shorter, or don't have to deal with the maximum amount of characters? 

Thank you very much in advance!

0

• 

  Eric Cauan Pasos

  October 29, 2021 05:05 Edited

  Hi there,

  The Cloudinary feature that could support the shortening of the delivery URL is the use of named transformation. But it does not cover the use case of having a long base64 encoded URL, in particular, the multiple/nested fetches of the same asset. 

  Also, there is a standard limit on the length of the URL address, but in your case, we could extend this to a certain value. In order to proceed and as we needed additional information, can you please help to open a support ticket here (https://support.cloudinary.com/hc/en-us/requests/new) so we can process your request?

  Thanks.

  Best regards,

  Eric

  0

Post is closed for comments.