jason
CDCloudflare Developers
•Created by jason on 4/18/2024 in #workers-help
Cannot get image transformations to work with S3 proxy.
So the solution for me was to remove the headers from the signing request when an image transformation was being done.
6 replies
CDCloudflare Developers
•Created by jason on 4/18/2024 in #workers-help
Cannot get image transformations to work with S3 proxy.
I finally figured it out. For anyone who comes looking afterwards. I was on the right track with the Authorization header - but I didn't realize that when the request is signed - it signs all of the headers - and if they don't match up, the signature verification will fail.
6 replies
CDCloudflare Developers
•Created by jason on 4/18/2024 in #workers-help
Cannot get image transformations to work with S3 proxy.
My S3 backend (not actually S3, but an S3 compatible service) doesn't have the option to turn off secure images.
6 replies
CDCloudflare Developers
•Created by jason on 4/18/2024 in #workers-help
Cannot get image transformations to work with S3 proxy.
I did find this thread: https://community.cloudflare.com/t/problem-with-cloudflare-worker-image-on-specific-datacenter-cph-ams-and-fra-is-working-fine/575660
Which seems to suggest that some CF endpoints will rewrite urls from https to http and that's what is causing the issue.
6 replies
CDCloudflare Developers
•Created by jason on 4/18/2024 in #workers-help
Cannot get image transformations to work with S3 proxy.
I may have made a small discovery. I noticed that when I was signing the request, it was producing a request that had a Authorization header. I had read elsewhere that Image Transformations didn't work with cookies/sessions/headers/etc. So I updated the signing request to put it all in the URL.
The signing still works - now without any headers (I've double checked the signed urls). And now I'm getting this:
ERROR 9408: Could not fetch the image — the server returned HTTP error 400 Bad Request6 replies