➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaswdr
Recipients jaswdr, ueJone
Date 2021-05-11.20:43:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1620765807.13.0.9597173482.issue44107@roundup.psfhosted.org>
In-reply-to
Content 
@ueJone according to the (RFC)[https://datatracker.ietf.org/doc/html/rfc6455#section-1.4] the FIN/ACK is not normative, in other words is recommended but not required, I've checked the syscalls of the server, see it below:

```
...
1561 15143 write(2, "127.0.0.1 - - [11/May/2021 20:08"..., 60) = 60$
1562 15143 sendto(4, "HTTP/1.0 200 OK\r\nServer: SimpleH"..., 154, 0, NULL, 0) = 154$
1563 15143 sendto(4, "<!DOCTYPE HTML PUBLIC \"-//W3C//D"..., 728, 0, NULL, 0) = 728$
1564 15143 shutdown(4, SHUT_WR)              = 0$
1565 15143 close(4)                          = 0$
...
```

As you can see, Python is not the one sending or not sending the ACK/FIN codes, this is coming from the underlining OS implementation of the `close()`.

My questions is, which OS are you using/testing this example?
History
Date User Action Args
2021-05-11 20:43:27jaswdrsetrecipients: + jaswdr, ueJone
2021-05-11 20:43:27jaswdrsetmessageid: <1620765807.13.0.9597173482.issue44107@roundup.psfhosted.org>
2021-05-11 20:43:27jaswdrlinkissue44107 messages
2021-05-11 20:43:26jaswdrcreate