Some time the response "just hangs.."

[AlmogBaku]

I don't know why yet, but sometime when I'm doing a request (specifically to this url) it just hangs.
Either from browser or curl:

curl --proxy-user user:pass --proxy myproxy.com:8080 http://m.booking.com/

Proxy logs:

2016/08/10 09:22:16 [110] INFO: Got request / m.booking.com GET http://m.booking.com/
2016/08/10 09:22:16 [110] INFO: Sending request GET http://m.booking.com/

Useless to say that without proxy it works as a charm.. (and booking.com is big enough to assume their servers probably well)

[elazarl]

Hmmm...

many thanks for the report.

I won't have time to investigate it in the next few weeks, but can you
attach a pcap, both of client->proxy and proxy->booking.com

On Wed, Aug 10, 2016 at 12:26 PM, Almog Baku notifications@github.com
wrote:

I don't know why yet, but sometime when I'm doing a request (specifically
to this url) it just hangs.
Either from browser or curl:

curl --proxy-user user:pass --proxy myproxy.com:8080 http://m.booking.com/

Proxy logs:

2016/08/10 09:22:16 [110] INFO: Got request / m.booking.com GET http://m.booking.com/
2016/08/10 http://m.booking.com/2016/08/10 09:22:16 [110] INFO: Sending request GET http://m.booking.com/

Useless to say that without proxy it works as a charm.. (and booking.com
is big enough to assume their servers probably well)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#178, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP4okIbqtmt4VtOkjmuURub_vrLEHmdks5qeZlQgaJpZM4Jg8zJ
.

[AlmogBaku]

From proxy. (Notice that the proxy is on a dedicated container.. this logs are from it's host)
http-booking-extracted.pcap.zip

[AlmogBaku]

It seems from there that the proxy keep the connection open until the end-server just stop to answer..
https://www.w3.org/Protocols/HTTP/Issues/http-persist.html

[AlmogBaku]

Squid defines a timeout for idle connections to the servers: http://www.squid-cache.org/Versions/v3/3.1/cfgman/pconn_timeout.html

[elazarl]

In principle all outbound connection goes through http.Transport, so it
should manage idle connection pools, timeouts, and the like. And of course
inbound connections by Go's http.

So I'm not sure we need anything specific.

On Thu, Aug 11, 2016 at 9:49 AM, Almog Baku notifications@github.com
wrote:

Squid define a timeout for idle connections to the servers:
http://www.squid-cache.org/Versions/v3/3.1/cfgman/pconn_timeout.html

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#178 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP4otFLEOxvYMPbtogTb86OXoI4drXlks5qesXrgaJpZM4Jg8zJ
.

[AlmogBaku]

golang/go#13998

[AlmogBaku]

seems like it should be fixed in 1.7+