You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that /endpoint is a local address that takes 300 seconds to finish. I mocked this.
What did you expect to see?
A proxied response.
What did you see instead?
Times out if /endpoint takes too long to reply (eg. due to long-polling). The proxy seems to completely drop the response (but oddly enough, only after 300 seconds). Curl'ing the /endpoint on the Go server results in a "curl: (52) Empty reply from server", even though data should be written out.
The text was updated successfully, but these errors were encountered:
mikioh
changed the title
ReverseProxy timeout
net/http/httputil: ReverseProxy timeout
Jan 20, 2015
It seems like your issue depends on your proxy and long-polling HTTP server stuff. Can you provide a simple, minimum reproducible example code for both entities?
mikioh
changed the title
net/http/httputil: ReverseProxy timeout
net/http/httputil: timeout on ReverseProxy that bridges long-poll conversations
Jan 20, 2015
What version of Go are you using (go version)?
go version go1.3.3 darwin/amd64
What operating system and processor architecture are you using?
OS X Yosemite
What did you do?
I'm proxying a long-polling request using:
Note that /endpoint is a local address that takes 300 seconds to finish. I mocked this.
What did you expect to see?
A proxied response.
What did you see instead?
Times out if /endpoint takes too long to reply (eg. due to long-polling). The proxy seems to completely drop the response (but oddly enough, only after 300 seconds). Curl'ing the /endpoint on the Go server results in a "curl: (52) Empty reply from server", even though data should be written out.
The text was updated successfully, but these errors were encountered: