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
We have a bucket object with a a space in it's key
valkey="my object"S3Client.download(bucket, key)
fails with the following error
akka.http.scaladsl.model.IllegalUriException: Illegal URI reference: Invalid input ' ', expected '/', 'EOI', '#', '?' or pchar (line 1, column 34): /waylay.plugins/app.templates/CO2 OK template
^
at akka.http.scaladsl.model.IllegalUriException$.apply(ErrorInfo.scala:40)
at akka.http.scaladsl.model.Uri$.fail(Uri.scala:752)
at akka.http.impl.model.parser.UriParser.fail(UriParser.scala:80)
at akka.http.impl.model.parser.UriParser.parseUriReference(UriParser.scala:45)
at akka.http.scaladsl.model.Uri$.apply(Uri.scala:209)
at akka.http.scaladsl.model.Uri$.apply(Uri.scala:181)
at akka.stream.alpakka.s3.impl.HttpRequests$.requestUri(HttpRequests.scala:111)
at akka.stream.alpakka.s3.impl.HttpRequests$.akka$stream$alpakka$s3$impl$HttpRequests$$s3Request(HttpRequests.scala:87)
at akka.stream.alpakka.s3.impl.HttpRequests$.getDownloadRequest(HttpRequests.scala:39)
at akka.stream.alpakka.s3.impl.S3Stream.request(S3Stream.scala:93)
at akka.stream.alpakka.s3.impl.S3Stream.download(S3Stream.scala:63)
at akka.stream.alpakka.s3.scaladsl.S3Client.download(S3Client.scala:50)
the case with a key of for example "my dir/my object.json" should also work (no encoding of the /'s)
when manually replacing " " with "%20" I get 403 Forbidden which indicates the signing is also broken with these kinds of url's
(the official client happily accepts keys with spaces)
The text was updated successfully, but these errors were encountered:
We have a bucket object with a a space in it's key
fails with the following error
the case with a key of for example "my dir/my object.json" should also work (no encoding of the
/
's)when manually replacing
" "
with"%20"
I get 403 Forbidden which indicates the signing is also broken with these kinds of url's(the official client happily accepts keys with spaces)
The text was updated successfully, but these errors were encountered: