Can we pass complete URL to the image resizer?

[sh-soltanpour]

Hey,
I just wanted to know if a URL like this is supposed to work or not? the first part is the image resizer URL and the second part is the bucket URL.
https://d2sv1t07lr5mwo.cloudfront.net/fit-in/3840x3840/filters:quality(100):format(webp)/https://d2q2ljtwokgf7a.cloudfront.net/media/images/city-landing-pages/banner-images/toronto.jpg

We have an old serverless image resizer (created 4 years ago) that can handle this but recently, we created a new resizer (v6.5) that throws an error as you can see.
I want to know if this is a misconfiguration issue on the new resizer or it's how it's supposed to work in version 6.5.

Thanks!

[RobFerrer]

I can't tell you the details of why, but https://d2sv1t07lr5mwo.cloudfront.net/fit-in/3840x3840/filters:quality(100):format(webp)/media/images/city-landing-pages/banner-images/toronto.jpg looks like it works (without the domain in the source image path)

[sh-soltanpour]

Yeah that works, but our legacy code generates the links as I sent for some parts, so I just wanted to double check whether the problem is from my configuration or this format is just deprecated.

[simonkrol]

Hi @sh-soltanpour, I might need some more info to help here,

The old instance of SIH you had running, what version was it?

What is the purpose surrounding the CloudFront url in the latter half of the request? Is that a CloudFront distribution with your S3 bucket as the origin?

The current implementation of SIH expects that the S3 bucket used to host the source images is provided in the SOURCE_BUCKETS template parameter, and that the image key is provided as part of the URL path (like in Rob's answer).

I've done a quick look through the code of some previous versions, and I haven't found anything post Lambda->Typescript rewrite that would support URLs being included as the path.

Let me know,
Simon

[sh-soltanpour]

Hey @simonkrol , thanks for your response.

Actually, I can't find the version of the older one, I can only see that the runtime was Python 2.7 if it helps, and created around 2019.

We just have a legacy code that generates that URL format, and it stopped working when we created a new instance of image resizer and a new bucket. So I was just wondering if there's a misconfiguration in the bucket settings or if it was just an old version of the image resizer supporting this type of URL.

And yeah the latter half domain is our bucket and the first half is our image resizer domain.

So I wanted to check if the functionality is expected or if I have misconfigured something.

[simonkrol]

Hi @sh-soltanpour,

The functionality you're seeing is expected, it looks like 4 years ago with the release of v4 and alongside the Python->Typescript migration is when the ability to include a link to the image was removed. If you were looking not to change the legacy code that generates the URL, and the images being accessed are all present in the same S3 Bucket (which is the first value in the SOURCE_BUCKETS template parameter) you could try the following workaround:

Follow https://docs.aws.amazon.com/solutions/latest/serverless-image-handler/use-the-rewrite-feature.html to use the rewrite feature supported by SIH (Will need to change the Environment variables of the backend lambda function).

Replace REWRITE_MATCH_PATTERN with /^(.*)(https:\/\/.*?\.net)(.*)$/ and REWRITE_SUBSTITUTION with /$1/$3

This will result in SIH modifying the requests as they come in, removing any URL that starts with https:// and ends with .net from the request. This will achieve the same thing as not including the CloudFront url (Like in Rob's answer), without needing to modify the legacy code.

Let me know if that is sufficient for your use case,
Simon

[sh-soltanpour]

@simonkrol
Great, Thanks a lot for the helpful information!