Replies: 1 comment 1 reply
-
|
You might want to check the dedicated pattern discussion here: #36 Regarding Signature: this is not supported by this plugin. There was a dedicated addon which has been archived while there was no usage: https://github.com/FriendsOfShopware/FroshPlatformThumbnailProcessorImgProxy |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a question about using imgproxy as self-hosted with Docker:
In the plugin I can only specify the following:
available variables:
{mediaUrl}: https://cdn.test.de/
{mediaPath}: media/image/5b/6d/16/tea.png
{width}: 800
{mediaUpdatedAt}: 1716882050 (unix timestamp) or 0
Hence my question:
mediaUrl: isn't that from the imgProxy server?
mediaPath: is the path to the image on the Shopware server and the data comes from the plugin?
width: is the width, which then comes from the plugin?
mediaUpdatedAt: is the last date the image was uploaded to the server?
I know from an earlier version that you had to enter a key to authenticate yourself, but apparently you don't have to do that anymore.
This is specified in the standard:
{mediaUrl}/{mediaPath}?width={width}
Do I then just have to add my URL in front of it? Example: https://imgproxy.domain.de/{mediaUrl}/{mediaPath}?width={width}
or should you use the patterns from the documentation:
https://imgproxy.domain.de/_/rt:fit/w:{width}/h:0/g:sm/plain/{mediaUrl}/{mediaPath}
if I currently send something to the server I get this:
WARNING [2025-02-21T11:40:21Z] Completed in 290.009µs /https://shopdomain/media/86/ae/cd/1740135217/froshthumbnailprocessortestimage.jpg?width=200 request_id=g0KGc313SRa4F_qKGJ-QR method=GET status=403 client_ip=31.18.23.211 error="Invalid signature encoding"
Beta Was this translation helpful? Give feedback.
All reactions