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
Depending on how you start a connection, the Connection header may be unexpectedly set to close
Creating a new instance of Net::HTTP and then calling its request method (or any of its methods that call request, eg: get) will first set the Connection header to close (if it's not already set), then start the connection, and re-call itself
Where as initiating a request with class methods, or by manually starting a connection before calling request will not set the Connection header
As the default connection in HTTP 1.1 is keep-alive, having the Connection header silently set to close is unexpected
Depending on how you start a connection, the
Connection
header may be unexpectedly set toclose
Creating a new instance of
Net::HTTP
and then calling itsrequest
method (or any of its methods that callrequest
, eg:get
) will first set theConnection
header toclose
(if it's not already set), then start the connection, and re-call itselfWhere as initiating a request with class methods, or by manually starting a connection before calling
request
will not set theConnection
headerAs the default connection in HTTP 1.1 is
keep-alive
, having theConnection
header silently set toclose
is unexpectedExamples:
I've created a PR to fix this issue - #179
The text was updated successfully, but these errors were encountered: