You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 23, 2020. It is now read-only.
Here when an image comes in, it is being URL encoded even if the image was already URL encoded. This can cause 404s or 403s with S3 URLs. Would it makes sense to URL decode before processing images, or even dropping the encode all together since data coming from Wombat has likely already been encoded?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Here when an image comes in, it is being URL encoded even if the image was already URL encoded. This can cause 404s or 403s with S3 URLs. Would it makes sense to URL decode before processing images, or even dropping the encode all together since data coming from Wombat has likely already been encoded?
The text was updated successfully, but these errors were encountered: