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
Description of the Issue (and unexpected/desired result)
Connections made to Consul with the "Connection: close" header set are not closed by consul and the ephemeral ports remain in TIME_WAIT state for the timeout duration.
We noticed this after doing some testing with single-shot service discovery requests.
Reproduction steps
Make a request to any consul agent API endpoint with the "Connection: close" header present
Given we haven't heard anything based on our suggestions/questions above I'm going to close this issue, but I encourage you to comment and we can re-open it if you want to pick this up again.
Alternatively, if things have changed dramatically, feel free to create a new issue or PR.
Description of the Issue (and unexpected/desired result)
Connections made to Consul with the "Connection: close" header set are not closed by consul and the ephemeral ports remain in
TIME_WAIT
state for the timeout duration.We noticed this after doing some testing with single-shot service discovery requests.
Reproduction steps
Make a request to any consul agent API endpoint with the "Connection: close" header present
consul version
for both Client and ServerClient:
1.0.2
Server:
1.0.2
consul info
for both Client and ServerClient:
Server:
Operating system and Environment details
Linux REDACTED 3.10.0-327.36.3.el7.x86_64 #1 SMP Mon Oct 24 16:09:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Log Fragments or Link to gist
The text was updated successfully, but these errors were encountered: