4 ms·
Even if port 80 was unprivileged, wouldn't you still run into issues if multiple users attempted to bind to the same port? Really, what would the problem be wi
by haikuginger 9y ago
Even if port 80 was unprivileged, wouldn't you still run into issues if multiple users attempted to bind to the same port?
Really, what would the problem be with just deploying an nginx instance that listens on 80 and routes by domain?
- JBReefer 9y agoYeah, you'd have to do that, and then have permissions around routing, like we do with the filesystem today. I really like this idea, it's really elegant.
- mac01021 9y agoWell, someone has to administrate the nginx routing config, or there needs to be a mechanism for each webapp sitting behind the nginx to register itself as a forwarding target. What I want to know is why can't we get all the major web browsers to look for (and honor) SRV records, so that www.mydomain.com can transparently have the browser connect to port 30338 (or whatever port my app is listening on). Then we dispense with the need for proxies altogether.
- eximius 9y agoAll major protocols should, IMO.
- phaer 9y agoNo problem at all, given that the underlying operating system would already require that somebody got privileged access. The point of the article as I understand it, isn't so much about the possibility of shared web hosting - it's obviously possible. It's more about how early design decisions shape our paradigms and the way we understand computing and the necessary resources.