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
Due to the effect of #950, custom stream wrappers like that registered with the Amazon S3 SDK , which registers s3:// can no longer be used.
Should we consider allowing the supported streams for images to be configured (with a warning about using insecure streams), while defaulting to the current allowed streams?
The text was updated successfully, but these errors were encountered:
Due to the effect of #950, custom stream wrappers like that registered with the Amazon S3 SDK , which registers
s3://
can no longer be used.Should we consider allowing the supported streams for images to be configured (with a warning about using insecure streams), while defaulting to the current allowed streams?
The text was updated successfully, but these errors were encountered: