News for hackers. Stuff that matters.
Re:Certificates for localhost by eximius on Wednesday June 20, 2018 @07:02PM (#17360681)
It would be neat if you could listen to a unix domain socket and have a simple way to specify that as an endpoint for an http URI.

i.e.,

http://[uds/path/to/uds.socket]

I reuse ipv6's current syntax here just for the example. A lot of bikeshedding would be needed. It would also be ugly to expose those kinds of internals to an end user, so you'd need some additional technology on top of this to look pretty.

Re:Certificates for localhost by inopinatus on Wednesday June 20, 2018 @07:42PM (#17360911)
There is an unofficial unix: URI scheme. Browsers don't support it but system clients sometimes do, for example nginx when configuring upstream groups as a reverse proxy[1].

[1] http://nginx.org/en/docs/http/ngx_http_upstream_module.html

Re:Certificates for localhost by eximius on Thursday June 21, 2018 @09:05AM (#17364678)
But that doesn't specify protocal then, does it?

I.e., http://unix:/path would be very not backwards compatible

Re:Certificates for localhost by sligor on Thursday June 21, 2018 @01:31PM (#17367323)
a '+' is a valid character in an URI scheme

then http+unix:///path would make more sense