Getting 404
I am not getting the difference between these two images as i am able to access the 2nd but but not able to access the 1st one. In first url it is automatically adding "v1/%20" due to which it causing problem.
-
Hi Prakash,
You are correct in that the '%20' is affecting the problematic image. This needs to be removed as our system is looking for a public ID with a space in the beginning and that does not match the actual public ID of the image - hence why the first public ID works. The link does also work with v1 included, it is just the space that is throwing off the system as displayed here:
http://res.cloudinary.com/meddo-healthcare/image/fetch/h_2200,w_1700/fl_relative,h_0.7,l_fetch:aHR0cHM6Ly9zMy5hcC1zb3V0aC0xLmFtYXpvbmF3cy5jb20vYXAtc291dGgtMS1lbXItc2NyaWJibGVzLzE1NTM2Nzc3ODI3MDMtcHJlc2NyaXB0aW9uXzEucG5n,w_1.0/v1/https://res.cloudinary.com/meddo-healthcare/image/fetch/https://s3.ap-south-1.amazonaws.com/ap-south-1-emr-scribbles/1549620555750-img-20170105-wa0004-250x250.jpg
However is there a reason you're re-fetching fetched images from your account? If there is a particular use case you have we would be happy to help as we don't always recommend fetching images from yourself.
Hope this helps!0
Post is closed for comments.
Comments
1 comment