-
Notifications
You must be signed in to change notification settings - Fork 641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty S3Exception #1589
Comments
Thank you for reporting, it would be perfect if you could prepare a PR to fix it. |
MarcinAman
added a commit
to MarcinAman/alpakka
that referenced
this issue
Jun 11, 2019
MarcinAman
added a commit
to MarcinAman/alpakka
that referenced
this issue
Jun 11, 2019
MarcinAman
added a commit
to MarcinAman/alpakka
that referenced
this issue
Jun 11, 2019
MarcinAman
added a commit
to MarcinAman/alpakka
that referenced
this issue
Jun 12, 2019
MarcinAman
pushed a commit
to MarcinAman/alpakka
that referenced
this issue
Jun 12, 2019
MarcinAman
added a commit
to MarcinAman/alpakka
that referenced
this issue
Jun 12, 2019
2m
added a commit
that referenced
this issue
Jun 12, 2019
Fixed in #1748 |
cheleb
pushed a commit
to cheleb/alpakka
that referenced
this issue
Jul 5, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Alpakka version: 1.0-M3
Expected Behavior
If S3 responds with an empty response (because of empty string key/secret). I would expect a useful error message but you get an empty S3Exception
Actual Behavior
Related tickets
There are related issues:
#731 (xml parse of empty body)
#731 (similar with wrong fix?)
Reproducible Test Case
Just provide an empty key ans secret to the S3Settings and try
getObjectMetadata
Preferably it would check/show the http response status if it's not 200 / if it encounters an empty body so that the user at least has a clue what the source of this error might be.
The text was updated successfully, but these errors were encountered: