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
Unfortunately, our S3 implementation is dependent on another system, which means that there is a backslash in the access key. If you create an absolute URI for a path, this leads to problems because backslash is an illegal URI character.
Steps To Reproduce
Initialize an S3 file system with a backslash in the access key, for example <ad\accesskey>
Create an absolute path or URI for a path
Expected Behavior
Get an absolute path/URI
Question
Is the user info (<>@) in the URI even necessary?
The text was updated successfully, but these errors were encountered:
Doesn't escaping the \ character in the access key uri segment with \\ work for this case?
Re:question:
TL;DR - yes, it's necessary for the time being. You might want to have multiple instances that use different buckets, so yes. We have plans to refactor this at some point so it's a bit more convenient to use, but for now it's necessary.
Bug Description
Unfortunately, our S3 implementation is dependent on another system, which means that there is a backslash in the access key. If you create an absolute URI for a path, this leads to problems because backslash is an illegal URI character.
Steps To Reproduce
Expected Behavior
Get an absolute path/URI
Question
Is the user info (<>@) in the URI even necessary?
The text was updated successfully, but these errors were encountered: