How does web browsing in a terminal services session work?

Question

Specifically, how does the data from a web server get routed to the correct session when it is sent back to the terminal server.

Is the session ID sent as part of the HTTP headers?

There's a very good reason I need to know, but it's fairly complicated and not particularly relevant to the question.

HTTP uses TCP/IP to send data over a network. TCP/IP works by using both a source port and destination port. Most people are familar with destination ports (http=80, https=443, smtp=25, etc). Before a connection can be established, the OS provides the application with a source port to send data out of to the destination port. When the response comes back, it's destination was the other packets source port. — Erik Philips
Thanks for the comment Erik. So from that am I correct to assume that in a terminal services environment, browsers running in separate sessions will all be assigned different ports with which to send data out of? — user3757455
Sessions make no difference, this occurs on just about any OS for any tcp/ip connection. This occurs on every request from a browser, even when browsers request files in parallel on a non-terminal server (each request has it's own source port). — Erik Philips

user3757455 user3757455 · Accepted Answer · 2014-10-29T13:04:28

0

votes

Answered by Erik Philips in comments above.