configurations for which part? (Note: I think I have shared plenty of configs above)
tanweerdev
Eiji
Nvm, I just looked at similar issues and people in other libraries were declaring for example port where it was not needed to.
Just for example:
https://github.com/minio/minio-js/issues/701#issuecomment-418078532
This shows that’s really hard to guess what’s the problem. There may be many reasons for that.
0
Eiji
Hmm … on the other side in this issue:
https://github.com/request/request/issues/2047
people are talking about changing request headers …
I don’t have an AWS-based project right now. Do you think you can try those suggestions? Maybe AWS does not supports some headers like those mentioned in issue …
Maybe easier would be to compare working request (like curl) with current one?
0
tanweerdev
Thanks for the help. But looks connection is being closed before even response was sent back to client. I tried few combinations from below configs
config :cybord, CybordWeb.Endpoint,
url: [host: "localhost"],
http: [
port: 4000,
protocol_options: [
# request_timeout: 60000,
inactivity_timeout: 60000, # 60000 millisecods equals one min
max_request_line_length: 99_999_999_999,
idle_timeout: :infinity
]
],
if I have inactivity_timeout: :infinity, it will process all the files but will not send back response even after processing it. I found this article helpful but even this doesnt provide details about the protocol possible options. As soon as All tasks are processed via async_stream (I have also tried to use chunk of 4 and then do task await or Task.async_stream) I need to insert some record in db and send back response. So in my opinion solution lies in http protocol options but as documentation is not very clear. I cant figure out how to achieve this. Thanks in advance for all the effort and help @Eiji
Related article: Dealing with long-running HTTP Requests and Timeouts in Phoenix
and options: https://ninenines.eu/docs/en/cowboy/2.5/manual/cowboy_http/
0
Eiji
ok, so most probably it’s not about content size except there is some limit on S3, but I don’t think it’s that as I believe that it should return a proper error response …
I have one more idea … Can you please compare result of:
S3.put_object(component_bucket(), destination_path, file)
with this documentation:
If it’s not that then I don’t think it’s possible to debug it properly at least from your app … Maybe we would need to debug some values in ex_aws code to have more information about request …
0