Closed bendubuisson closed 3 years ago
I would check out issue #33 and #43 as those should cover what you need. Essentially the preview links add a version ID to the query string which will break a signed request to view a protected asset
@obj63mc ha that makes a lot of sense as I was able to acces signed requests of protected assets when using AbsoluteLink
, will check it out thanks!
Shouldn't that be fixed in 1.1.0 though?
So I confirmed it is due to the vid=
appended to the image, but I thought that was fixed in 1.1.0?
With our 1.1.0 we just set the default config values to not bust cache in asset admin in _config/assetadmin.yml. It would depend on what version of asset admin you are using whether the config value would actually work or not. If you are on the latest version then I would request that https://github.com/silverstripe/silverstripe-asset-admin/issues/1026 be reopened
Fixed with silverstripe/asset-admin
1.8 and
SilverStripe\AssetAdmin\Controller\AssetAdmin:
bust_cache: false
Thank you!
Should it be part of the doc?
Cheers
There seems to be an issue with the preview link generated:
Instance has all access to S3, as it can write etc, so it's somehow the generated link for preview that has a problem.
It seems that error message is quite cryptic and could be a range of things...
I rely on policies to access S3, so I have not explicitly set keys, my next step is to try that. Every other Action works though which is why it's weird...