In a TCP conversation, if a server initiates a disconnect by sending a FIN to the Client, the server enters FIN-WAIT-1 state. If the Client then sends an ACK he enters the Close-Wait state and the server is now in FIN-WAIT-2 state. At that point the servers is expecting that the Client will follow up with a FIN, which he will ACK thus ending the conversation.
Is the Client allowed to send a POST instead of a FIN, and force the TCP conversation to stay open?
I didn't think so but Akamai tells me it's Kosher.
We have situation after situation where we disconnect and everything works fine:
1. Svr-Fin -->
2. Cli-Ack -->
3. Cli-Fin -->
4. Svr-Ack -->
With one particular application we have this error that keeps popping up because Akamai sends an Ack in step two but a POST in step three...(which we respond to with a Reset causing an error).
Is sending a POST after Acking a FIN allowed in TCP?
Is the Client allowed to send a POST instead of a FIN, and force the TCP conversation to stay open?
I didn't think so but Akamai tells me it's Kosher.
We have situation after situation where we disconnect and everything works fine:
1. Svr-Fin -->
2. Cli-Ack -->
3. Cli-Fin -->
4. Svr-Ack -->
With one particular application we have this error that keeps popping up because Akamai sends an Ack in step two but a POST in step three...(which we respond to with a Reset causing an error).
Is sending a POST after Acking a FIN allowed in TCP?
