Replication job might be hang when doing copy to some big blobs (after enable tls)

[steven-zou]

The response body is returned to the push blob function for reading from the pull blob function that is for writing.

The issue might be caused by the underlying golang library, there are some issues may be related to this issue:

• x/net/http2, net/http: client can hang forever if headers' size exceeds connection's buffer size and server hangs past request time golang/go#23559
• x/net/http2: pool deadlock golang/go#32388
• x/net/http2: Blocked Write on single connection causes all future calls to block indefinitely golang/go#33425
• net/http: a "bad" https connection which uses Header.Set could potentially block all https requests more than 15 mins in production environments golang/go#33006

[bitsf]

Manually create the http client like this can fix the replication hang. It seems the main different with http.DefaultTransport is param ForceAttemptHTTP2=false

[steven-zou]

Fixed in PR #11645.

Close this issue now.