Re: [go-nuts] Unsolicited response received on idle HTTP channel...

872 views
Skip to first unread message

Dave Cheney

unread,
May 21, 2013, 6:38:06 PM5/21/13
to col...@boundary.com, golang-nuts
Is it possible this is a symtom of issue 5522 ?

On Fri, May 17, 2013 at 6:35 AM, <col...@boundary.com> wrote:
> I've written a program whose goal is to execute many millions of http
> requests. To achieve this i create a new http client like so:
>
> func newHttpClient() *http.Client {
> transport := &http.Transport{
> MaxIdleConnsPerHost: 50,
> DisableCompression: true,
> }
> return &http.Client{Transport: transport}
> }
>
> Periodically, as it runs, I see in the log:
>
> 2013/05/16 20:16:13 Unsolicited response received on idle HTTP channel
> starting with "H"; err=<nil>
>
> It was much more frequent without DisableCompression: true, but it's still
> popping up.
>
> This is running on the latest tip, linux/amd64.
>
> Any ideas on how to understand this?
>
>
> --
> 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...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Skip Tavakkolian

unread,
May 29, 2013, 6:39:26 PM5/29/13
to Dave Cheney, col...@boundary.com, golang-nuts
that bug report says its a bug in nginx; so the http server in the sdk suffers from the same bug?

FWIW, it also happens on 1.8.0 for macosx (amd64).

Dave Cheney

unread,
May 30, 2013, 9:01:34 PM5/30/13
to Collin Van Dyck, golang-nuts
On Fri, May 31, 2013 at 10:43 AM, <col...@boundary.com> wrote:
> Dave, yes, this seems like an nginx bug (that's what I was accessing via the
> http client) that's fixed in 1.1.1. Thanks for the pointer :-)

Point of order, the workaround in tip is not going to be included in 1.1.1.

>
> Skip, no, I was not using the http server in the SDK.

Collin Van Dyck

unread,
May 30, 2013, 9:08:30 PM5/30/13
to Dave Cheney, golang-nuts
Ah, ok, I must have mis-read the bug tracker notes. Thanks for the update.
Reply all
Reply to author
Forward
0 new messages