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
When an Armeria client sends the HEAD / upgrade request, some HTTP/1 servers send a 404 response with a Connection: close header instead of keeping the connection alive. The Armeria client attempts to send an HTTP/1 request for the current invocation to the closed connection after receiving the rejected upgrade response, which is incorrect and thus raises a SessionClosedException.
To fix this issue, we could make Armeria client handle Connection: close header properly and remember the list of the hosts that rejected the upgrade request.
When an Armeria client sends the
HEAD /
upgrade request, some HTTP/1 servers send a 404 response with aConnection: close
header instead of keeping the connection alive. The Armeria client attempts to send an HTTP/1 request for the current invocation to the closed connection after receiving the rejected upgrade response, which is incorrect and thus raises aSessionClosedException
.To fix this issue, we could make Armeria client handle
Connection: close
header properly and remember the list of the hosts that rejected the upgrade request.(Originally reported by @anuraaga)
The text was updated successfully, but these errors were encountered: