"Unsolicited response received on idle HTTP channel starting with "0\r\n\r\n"; err=<nil>"

[PDVJAM]

I have built ipfs with this plugin, and everything works fine, I see my files in S3 bucket. But in logs I see a lot of " Unsolicited response received on idle HTTP channel starting with "0\r\n\r\n"; err=" messages. What might cause them? And how to fix? Any ideas?

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[aschmahmann]

@MichaelMure any ideas/thoughts?

[guseggert]

Ultimately the cause is that something is violating the HTTP state machine. In golang/go#19895 this happened on a HEAD request that returned a chunked-encoded body...the Go HTTP client read the head request but not the body, since HEADs don't have bodies. The leftover bytes aren't a valid HTTP message, hence the error. go-ds-s3 does issue HEAD reqs for GetSize calls, so it might be that, or something else.

If you are still having this issue, try turning on debug logging in the AWS SDK to show the HTTP reqs and responses. If server responses look fine then it is likely a bug somewhere client-side.

[MichaelMure]

@aschmahmann I don't see any logs like that in our systems.