Adding a socket handler for keep TCP connection #3422
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is not http keepalive option it is TCP level which is lower than HTTP. It will send meanless ack flag packet to server. so it woudn't be drop TCP connection by server side like Firewall, Loadbalancer, Nginx etc.
|
The feature is a lot special. #2808 (comment) may give you some inspirations. |
mbargiel
pushed a commit
to mbargiel/axios
that referenced
this pull request
Jan 27, 2022
This is not http keepalive option it is TCP level which is lower than HTTP. It will send meanless ack flag packet to server. so it woudn't be drop TCP connection by server side like Firewall, Loadbalancer, Nginx etc. Co-authored-by: Jay <jasonsaayman@gmail.com>
This was referenced Feb 22, 2022
This was referenced Mar 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is not a http keepalive option. It is TCP level which is lower than HTTP.
It will send meanless ack flag packet to server.
so it wouldn't be dropped TCP connection by server side
like Firewall, Loadbalancer, Nginx etc.
Behavior overview
Before behavior
As you see the connection closed by server (RST falg)
After behavior
Server didn't close the connection because ping pong ACK flag packets.
Actually this is a general behavior in web browsers