This support forum is no longer in use. Please use the Cloudinary Community at https://community.cloudinary.com/ to receive assistance from other members of the community and from Cloudinary's support team. For account-specific questions or if you believe that you've encountered a bug, please contact the Cloudinary team directly via the "submit a request" option on this support site.

400 Bad Request when requesting large images

Follow
Avatar
Erik Sharp

Hello,

I am attempting to download an image with the following format:

http://res.cloudinary.com/<my-account>/image/upload/w_2300,c_scale,dpr_3.0,f_auto,q_auto/v1515293004/Error/IMG_3674.jpg

This came from the data-src:

 
The image that it is attempting to download would obviously be massive - much larger than the originally uploaded size of 1600 X 1200.
 
Instead of either of either doing an upscale transformation or better yet, just delivering the original size, I am getting a 400 Bad Request.
 
Am I missing something?
 
Thanks
0

Comments

3 comments

Sort by Date Votes
  • Avatar
    Roee Ben Ari

    Hi Erik, 

    In general, there is a total of MP (megapixels) limit, which likely to be the reason your URL fails to process. 

    In order to understand your specific issue, could you please share your cloud name as well? If you want to keep this data private, please feel free to open a support ticket and we'll continue from there.

    0
    Comment actions Permalink
  • Avatar
    Erik Sharp

    Sure, my cloudinary name is alonganotherpath.

    I can definitely understand the need for a MP limit, but it would seem logical that when a request is made that is either:

    1. Bigger than a MP limit

    or

    2. Bigger than the source image

    ...that the server would just send the size of the original image as a maximum.

    0
    Comment actions Permalink
  • Avatar
    Roee Ben Ari

    Hi Erik,

    Thanks for sharing your cloud-name and for the feedback. 

    The error you received is as follows:

    ImageTooLarge: Maximum image size is 25 Megapixels. Requested 35.71 Megapixels

    The reason we're not sending a fallback size is that the client usually expects a specific size to return and returning a different one might mess things up. Errors, on the other hand, can be handled and monitored. 

    That said, I'll share your insights internally for further review. 

    Thanks!

    0
    Comment actions Permalink

Post is closed for comments.