Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: HTTPS support #6

Open
mikescott opened this issue Feb 25, 2020 · 1 comment
Open

Feature request: HTTPS support #6

mikescott opened this issue Feb 25, 2020 · 1 comment

Comments

@mikescott
Copy link

Please would you be able to add support for _https._tcp services? I would like to advertise services such as my Unifi controller and Proxmox interface, both of which require HTTPS. Currently these aren't detected by LocalSites as it only supports _http._tcp.

@plan44
Copy link
Owner

plan44 commented Feb 25, 2020

Hi Mike,

LocalSites intentionally does not support _https._tcp, for the following reason (from the service types registry, emphasis mine:

https: HTTP over SSL/TLS
Tim Berners-Lee
Protocol description: RFC 2616

NOTE: Web browsers like Safari and Internet Explorer (with the Bonjour for Windows plugin)
DO NOT browse for DNS-SD service type "_https._tcp" in addition to browsing for "_http._tcp".

This is a conscious decision to reduce proliferation of service types, to help keep
DNS-SD efficient on the network. Today, if a user types http://www.mybank.com/ into their
web browser, the web server automatically redirects the user to https://www.mybank.com/.
Rather than having an entirely different DNS-SD service type for https, we recommend
using the same redirection mechanism: advertise a plain "http" service, which consists
of nothing except an HTTP redirection to the desired "https" URL.

Work is currently being done on adding mechanisms to HTTP and TLS to allow the server
to tell the client that it needs to activate TLS on the current connection before
proceeding. If this becomes widely adopted, it further justifies the decision to
not create a separate DNS-SD service type "_https._tcp", because security becomes
just another one of the things that is negotiated on a per-connection basis (like
content-type negotiation today) rather than being an entirely separate thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants