could be similar to #546 , where special s3 path parsing breaks reaching an object
s3 objects with ? in the key are unreachable from ex_aws
It's true that S3's key naming strongly recommends against including ? in keys, but it allows and handles them all the same, and they're still accessible via its cli. Alas, in our case the mistake has already been made :)
Environment
Current behavior
could be similar to #546 , where special s3 path parsing breaks reaching an object
s3 objects with
?
in the key are unreachable fromex_aws
It's true that S3's key naming strongly recommends against including
?
in keys, but it allows and handles them all the same, and they're still accessible via its cli. Alas, in our case the mistake has already been made :)Expected behavior
s3 objects with
?
would ideally be reachable