|
|
|
|
|
|
by _nalply
522 days ago
|
|
|
Good idea if you host a server, but then probably you also could employ HTTP/2 which doesn't have this limitation. If you offer an executable where the end-user runs it on their own laptop or desktop, you can't expect them to configure multiple domains, but probably there's a way to work-around that: have multiple localhosts like 127.0.0.1, 127.0.0.2, and so on, but there's still one limitation: if the end-user wants to run it on a home server, this won't work as well. In that case tell him to define multiple names for the home server. Ugh. |
|
|