Why not resolve everything with UNIX sockets instead, that way you can have them named and scoped instead, hiding behind port 443, since it's mosly HTTP anyway.

▲

tdeck 5 hours ago | parent [-]

Does this work in the browser? How will paths to different resources used by the web app work?

	▲	dvhh 4 hours ago \| parent [-]
		works with curl, maybe there is a case to either build a proxy for UDS and expose them to a browser, or open a request ticket to browser maintainers to support UDS