What about unrequited (client has died down) responses sent by the server

[sanjarcode]

1. Does HTTP/TCP have a mechanism to fail the response if this happens?

For example - I load a React app - multiple requests are made. I then close the tab. Does the server check this and pre-emptively cancel the response, or does it complete its cycle (waste of resources)? I have seen this happen with React and Vue dev servers - if you open a tab (local app) and close it fast and then open it again, the page is slow, since maybe the dev server is still responding to the non-existent tab.

2. Also, what does this nature mean in terms of 'statelessness' that's preferred in web apps? I think it won't affect anything, since it's a communication level thing, not a data level thing.
3. Is the concept of a 'heartbeat' relevant here? Or is it a different problem.