I'm working on an HTTP client integration that will allow Apache 5's async
client to be used as the HTTP backend for the AWS Java SDK [1]. One of the
first smoke tests I ran failed because the server responded to my request
with a TCP RST. I quickly realized that it was doing this because I was
sending an unencrypted request over port 443. To make things weirder, this
was taking place *after* a TLS session had been successfully negotiated.
I was having this problem on beta6, and I noticed that the most recent
commit to the client, 070f30fdc ("Fixed session i/o and wire logging in
async clients"), had modified some async wire logging code that I was
starting to grow suspicious of during my debugging. I upgraded to
beta7-SNAPSHOT, and sure enough, the problem went away. I'd like to get a
better idea of what the problem is, and in particular, why my other
HttpClient 5 integration doesn't seem to have this problem. (Is there a
workaround I can use on beta6?)
[1] https://github.com/aws/aws-sdk-java-v2
