I think the definition of "temporary" is the issue here. Something like an
underlying EAGAN is "temporary" - retrying the same operation that failed on
the same socket again can succeed. A read error from a closed TCP connection is
not temporary - reading again cannot possibly unclose the
Looking further into this, I see this as a typical transient error in a bad
network on downloading files. It may be different elsewhere, but I have to
retry on that error as it appears. And I cannot change the network
somewhere in the Guatemala outback.
On Monday, April 16, 2018 at 4:59:28 PM
On Mon, Apr 16, 2018 at 3:09 PM, Jens-Uwe Mager wrote:
>
> I am checking net.error for the Temporary() condition, and in my very bad
> network I do see really a lot of errors. While doing a GET request I see
> that
>
> http: unexpected EOF reading trailer
>
> is not a temporary
I am checking net.error for the Temporary() condition, and in my very bad
network I do see really a lot of errors. While doing a GET request I see
that
http: unexpected EOF reading trailer
is not a temporary error, so my retry logic does not kick in. Is this a
special case or just an