Protocol set to 1.1

[sinhaashish]

okhttp3.OkHttpClient uses default http2.0 by default, which has been changed to 1.1 as web server behaved incorrectly when HTTP/2 is enabled.
With http2.0 errors like okhttp3.internal.http2.StreamResetException: stream was reset: PROTOCOL_ERROR and okhttp3.internal.http2.StreamResetException: stream was reset: NO_ERROR arises

The resolution to this issue as suggested in community is to change the protocol to 1.1
Refer and thus this PR restricts the protocol to 1.1

Fixes #765
Fixes minio/minio#7501
[Fixes] (minio/minio#7501)
Refer

 public OkHttpClient.Builder protocols(List<Protocol> protocols)
Configure the protocols used by this client to communicate with remote servers. 
By default this client will prefer the most efficient transport available, falling back to more
 ubiquitous protocols. Applications should only call this method to avoid specific 
compatibility problems, such as web servers that behave incorrectly when HTTP/2 is enabled.

[harshavardhana]

The description is not elaborate, can you provide more details of the fix ?

[sinhaashish]

The description is not elaborate, can you provide more details of the fix ?

updated.

[harshavardhana]

I am still not sure if this is the right fix @sinhaashish - turning off http2.0 is perhaps not the solution here.

[deekoder]

@harshavardhana is there a recommendation for @sinhaashish

[harshavardhana]

@harshavardhana is there a recommendation for @sinhaashish

My recommendation is we talk to upstream Go first and report this issue to them and get their guidance on what might be happening. Since this issue is sporadic as well, we shouldn't default to HTTP 1.1 right away without much information.

[kannappanr]

LGTM

[harshavardhana]

Okay for the time being, please open another GitHub issue to trace back to the original problem here @sinhaashish - we need to follow up with Go upstream and circle back with a reproducer.

Since HTTP2.0 is important for our clients as much as for our servers.

[sinhaashish]

Go UpSTream Issue