Sockets are not listening on URLs but on a single port on one or all interfaces where the interfaces are defined by their IP adresses.
If you for example bind a listening socket to port 80 on the loopback interface 127.0.0.1, the corresponding address will be
"localhost:80".
When servicing HTTP requests on this socket, the URL will be
"http://localhost:80/".
If you want to service HTTP requests depending on the relative URI part, you need a server process that reads the request and forward it depending on the relative URI. In your previous question you have already used an API that provides such a technique:
About HTTP Server API (Windows)[
^].
It will create listening sockets internally and allows handling of the requests by additional functions.