Hello,
since updating the media_processing extension from version 0.9.0 to 0.10.0, our image proxy integration is broken for all newly processed files.
Any new image that is processed by TYPO3 results in a URL with an "Invalid signature" error from the image proxy service. Images that were already processed under v0.9.0 and exist in the sys_file_processedfile table continue to display correctly.
Downgrading the extension back to v0.9.0 immediately resolves the issue, and all images are processed with a valid signature again.
While we initially discovered this in a multi-domain setup, further testing has confirmed that this is a general issue and also occurs on simple, single-domain installations. It seems to be a fundamental problem with how signatures are generated in v0.10.0.
Hello,
since updating the media_processing extension from version 0.9.0 to 0.10.0, our image proxy integration is broken for all newly processed files.
Any new image that is processed by TYPO3 results in a URL with an "Invalid signature" error from the image proxy service. Images that were already processed under v0.9.0 and exist in the sys_file_processedfile table continue to display correctly.
Downgrading the extension back to v0.9.0 immediately resolves the issue, and all images are processed with a valid signature again.
While we initially discovered this in a multi-domain setup, further testing has confirmed that this is a general issue and also occurs on simple, single-domain installations. It seems to be a fundamental problem with how signatures are generated in v0.10.0.