In HTTP shared hosting, this trick is abstracted in the process of handling the HTTP conversation, which happens after the TCP conversation is started. A hostname is an application-level abstraction of an IP address, and at the Internet or Transport layers they hold no meaning.
I'll appreciate pointers to any reading material as well.Īt the IP level, there is no such thing as a hostname. If I wanted to write such a layer myself (since it may be a bit application specific), could it be done in java or node.js (I mean could it be done using higher level API or do I have to start taking apart ip packets)? How would I know which hostname the client connected to, since all host names resolve to the same machine?
#Psequel connect to hostname dynamically assigned software
Which software do I actually need? Does existing software allow such changes on demand (I have heard have firewall changes requiring a day)? While googling this info, I see references to firewalls, proxies, reverse proxies. I want to dynamically control how ports x, for host y actually point to port z on my physical machine. I want to redirect clients to their own ports based on which hostname they connect to.įor example, client1 connects to and is connected to port 1234.Ĭ -> 1235, -> 1236, etc. Say I have one machine and clients will make tcp (but not http!) connections to it. I'm a programmer trying to figure out some stuff beyond my domain:
0 kommentar(er)
