-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S3 GET Parameters not stripped #529
Comments
This is the url of cached image, is it? And do you want to strip those query parameters off? If so you can create a listener on POST_RESOLVE and do with the url whatever you need. |
@makasim I've tried with a listener which strips get parameters ath the post_resolve event but there are cases when this post_resolve event is not called. the following does not go through the resolve function, how can I handle that ? |
If the cache already exist, you are redirected to the cached image, by passing the filter action, indeed the post resolve event is not triggered. We may need a new listener which triggers before we resolved the cached image url |
We use S3 to store our images and use a temporary url to read them, this url obviously has a few extra parameters in it.
0ed3ab5ec2bd1fbaa44c4dbc4766205a.jpg?AWSAccessKeyId=<key>&Expires=1408614399&Signature=<signature>
This is fine when it goes into the cache manager for loading, but the cached file simply dumps that full url, into the filename, schema and get parameters included.
What's the best way around this? I would guess a transformation on the check of caching and the write of caching would be enough is this doable from outside the plugin?
The text was updated successfully, but these errors were encountered: