Actually, our error output is slightly different than issue 17066's. 

2017/07/14 10:53:31 http2: Transport failed to get client conn for 
<redacted>:443: http2: no cached connection was available
2017/07/14 10:53:31 http2: Transport creating client conn 0xc4200016c0 to 
<redacted>:443
2017/07/14 10:53:31 http2: Framer 0xc4202b41a0: wrote SETTINGS len=18, 
settings: ENABLE_PUSH=0, INITIAL_WINDOW_SIZE=4194304, 
MAX_HEADER_LIST_SIZE=10485760
2017/07/14 10:53:31 http2: Framer 0xc4202b41a0: wrote WINDOW_UPDATE len=4 
(conn) incr=1073741824
2017/07/14 10:53:31 http2: Transport encoding header ":authority" = 
"<redacted>"
2017/07/14 10:53:31 http2: Transport encoding header ":method" = "POST"
2017/07/14 10:53:31 http2: Transport encoding header ":path" = "/"
2017/07/14 10:53:31 http2: Transport encoding header ":scheme" = "https"
<redacted some x-headers>
2017/07/14 10:53:31 http2: Framer 0xc4202b41a0: read SETTINGS len=18, 
settings: MAX_FRAME_SIZE=1048576, MAX_CONCURRENT_STREAMS=250, 
MAX_HEADER_LIST_SIZE=1048896
2017/07/14 10:53:31 http2: Transport received SETTINGS len=18, settings: 
MAX_FRAME_SIZE=1048576, MAX_CONCURRENT_STREAMS=250, 
MAX_HEADER_LIST_SIZE=1048896
2017/07/14 10:53:31 http2: Transport encoding header "content-length" = 
"141"
2017/07/14 10:53:31 http2: Transport encoding header "accept-encoding" = 
"gzip"
2017/07/14 10:53:31 http2: Transport encoding header "user-agent" = 
"Go-http-client/2.0"
2017/07/14 10:53:31 http2: Framer 0xc4202b41a0: wrote HEADERS 
flags=END_HEADERS stream=1 len=212
2017/07/14 10:53:31 Unhandled Setting: [MAX_HEADER_LIST_SIZE = 1048896]
2017/07/14 10:53:31 http2: Framer 0xc4202b41a0: wrote SETTINGS flags=ACK 
len=0
2017/07/14 10:53:31 http2: Framer 0xc4202b41a0: wrote DATA stream=1 len=141 
data="<redacted>"
2017/07/14 10:53:31 http2: Framer 0xc4202b41a0: wrote DATA flags=END_STREAM 
stream=1 len=0 data=""
2017/07/14 10:53:31 http2: Framer 0xc4202b41a0: read SETTINGS flags=ACK 
len=0
2017/07/14 10:53:31 http2: Transport received SETTINGS flags=ACK len=0
2017/07/14 10:53:31 http2: Framer 0xc4202b41a0: read WINDOW_UPDATE len=4 
(conn) incr=141
2017/07/14 10:53:31 http2: Transport received WINDOW_UPDATE len=4 (conn) 
incr=141
2017/07/14 10:53:31 http2: Framer 0xc4202b41a0: read RST_STREAM stream=1 
len=4 ErrCode=INTERNAL_ERROR
2017/07/14 10:53:31 http2: Transport received RST_STREAM stream=1 len=4 
ErrCode=INTERNAL_ERROR
2017/07/14 10:53:31 RoundTrip failure: stream error: stream ID 1; 
INTERNAL_ERROR
2017/07/14 10:53:31 Post https://<redacted>/: stream error: stream ID 1; 
INTERNAL_ERROR

We get INTERNAL_ERROR instead of REFUSED_STREAM

On Friday, July 14, 2017 at 12:06:30 PM UTC+2, thwd wrote:
>
> Seems to be Mac OS related. It works on Linux, every time over HTTP 1 and 
> 2.
>
> On Friday, July 14, 2017 at 11:33:22 AM UTC+2, thwd wrote:
>>
>> We tried:
>>
>> if len(os.Getenv("DISABLE_HTTP2")) > 0 {
>>     http.DefaultClient.Transport = &http.Transport{
>>         TLSNextProto: make(map[string]func(string, *tls.Conn) 
>> http.RoundTripper),
>>     }
>> }
>>
>> But the effect was the same as with GODEBUG=http2client=0, just an EOF. 
>> Will keep trying.
>>
>> If it is relevant we're using "golang.org/x/crypto/acme/autocert" for 
>> TLS and our service is only reachable through HTTPS. The certificate is 
>> valid and working and will not expire soon.
>>
>> On Friday, July 14, 2017 at 11:10:39 AM UTC+2, thwd wrote:
>>>
>>> We use GKE (Kubernetes on GCE) and have Go HTTP/2 pods running there. In 
>>> front of them is a service of type "LoadBalancer". As I understand, these 
>>> are nginx instances.
>>>
>>> Since this week, the error described in issue 17066 [1] is happening 
>>> about 90% of the time when we connect a client via HTTP/2 (it works 
>>> sporadically).
>>>
>>> This project has been running for over a year with no issues until this 
>>> week. I suspect Google deployed an update or such to the load balancers.
>>>
>>> We've tried setting GODEBUG=http2client=0 (as described in package 
>>> net/http doc) to use HTTP 1.1 but all we get is a io.EOF error on 
>>> http.DefaultClient.Do.
>>>
>>> I'm working on a workaround, will post how we solve it. Any ideas or 
>>> suggestions are welcome.
>>>
>>> [1] https://github.com/golang/go/issues/17066
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to