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
I've noticed that the S3Iterator returns directory elements with an S3Path that is missing the / at the end of the key. With the results from the listobjects call, the code intentionally splits each returned object on the / and then feeds those elements to the S3Path. S3Path in turn build a URL, but then if would remove a / at the end if it exists.
What I don't understand is why? If a key ends with a / then its the only way to access that object.
The text was updated successfully, but these errors were encountered:
I've noticed that the S3Iterator returns directory elements with an S3Path that is missing the / at the end of the key. With the results from the listobjects call, the code intentionally splits each returned object on the / and then feeds those elements to the S3Path. S3Path in turn build a URL, but then if would remove a / at the end if it exists.
What I don't understand is why? If a key ends with a / then its the only way to access that object.
The text was updated successfully, but these errors were encountered: