Sergei Aleksandrovich

Hey @13MrBlackCat13! `https:/domain.tld/exemple.jpg` does not has a domain indeed. It looks like something in front of imgproxy normalized your URL.

What I meant to say is that an `https` URL should start with `https://`, not with `https:/`

Hey @K4CZP3R! It looks like Pi's CPU doesn't support optimizations imgproxy's dependencies are built with. Which is actually doesn't surprise me as ARM builds of imgproxy are made mostly for...

Hi Justas, Well, it looks easy. But. libvips uses ImageMagick for PSD. I'm not a fan of using IM for image loading, especially when the format is complex. Complex formats...

Hi Bernardo, > Do you mind clarifying which of the 12factor principles thumbor fails to achieve? If we are missing something it would be in our interest to improve. Thumbor...

Hi @approached! Do you mean multiple watermarks on a single image or different watermarks on different images?

Sorry for abandoning this issue. OSS version of imgproxy only allows you to specify a single watermark via config. imgproxy Pro allows specifying a custom watermark for every request.

Hey @UserFengFeng! Sorry for the delay. I tried your `docker-compose.yml`, and it works perfectly. Is this issue still actual?

Ugh, how I could possibly miss that? ``` http://10.0.0.174:8082/resize:fill:1000:1000:0/plain/http://10.0.0.174:6090/test1/xxx.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=95QP6GGLJ54PHPGCFJWJ%252F20220425%252Fus-east-1%252Fs3%252Faws4_request&X-Amz-Date=20220425T051958Z&X-Amz-Expires=604800&X-Amz-Security-Token=eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhY2Nlc3NLZXkiOiI5NVFQNkdHTEo1NFBIUEdDRkpXSiIsImV4cCI6MTY1MDg2NzU4NSwicGFyZW50IjoiYWRtaW4ifQ.J-zChUGFx4wF7RmEYoBhgVJ3vXPIx5FAltvnKPNEaMBx_-qIDhB64zr4d6HqrPaJs_2UCwXq8sXMPP5AaM-2XA&X-Amz-SignedHeaders=host&versionId=null&X-Amz-Signature=76773fb8ce096f96e15dd412ed6e9f44085f030102b944d330539c014573acb1 ``` @UserFengFeng your source URL contains a query string (the part after `?`), so the whole URL should be escaped. Otherwise,...

Hi Emil, As far as I see, Backblaze has access to the files by URL. if you need access to private files, you can set the `Authorization` header with `IMGPROXY_CUSTOM_REQUEST_HEADERS`...