I am trying to fill in gaps of my understanding of HTTPS.
I understand that the server sends the client a public key to encrypt information and that only the server has the private key which prevents interception of request packets.
What happens in the response side of things? E.g. web application server responds with a session token, or is responding with sensitive information. Could a MITM attacker catch the initial public key response from the server and pretend to be the intended client? Or does the client also have a private/public key that it uses to handle the responses, and passes the public key inside the request?
Basically wondering if you can pretend to be the client, instead of most MITM where the attacker pretends to be the server.