https://lakefs.io/ logo
Join Slack
Powered by
Hi, we are using `alpakka/s3` to upload/download o...
# help
t
Hi, we are using 
alpakka/s3
to upload/download object to lakefs, the problem is lakefs returns 
Content-Type: text/xml
header for S3 API, which our client does not accept (it expects 
application/xml
as real S3 API is returning). I've created an issue here https://github.com/treeverse/lakeFS/issues/987
a
That sounds like a good plan. I'll review it happily. If it's closer to real S3 then we should pull it today. Thanks!
Hi @Tâm Nguyễn Đức, I've readied https://github.com/treeverse/lakeFS/pull/992. I believe it should fix your issue, however, I do not have your client. Could you try it on your setup, or alternatively give me a client that generates this header? Note that it relies on the client generating a suitable 
Accept:
header in its requests. Given that application/xml and text/xml are both allowed by RFC, a client that accepts only one should specify which one it requires.
t
Hi, Unfortunately, alpakka does not send 
Accept
 header so this fix does not work for us. Currently we are using an work around (proxy the response to replace the response header) to overcome this issue.
a
I'm currently at a loss what to do. In your experience, would the akka project be receptive to a patch to add such a header? Alternatively, can you furnish their s3 client with a Request object that populates such a header? In any case I'd like to continue this discussion on the issue, if that's OK with you?
t
I think changing the client is not the way to go because it is currently working well with S3 itself, and other S3 emulators like minio.
a
Odd. So I shall see what minio does and try to copy that.
Open in Slack
PreviousNext
Powered by