Clipboard API over http (not https) to local intranet server
Does anyone know of a work around to enable clipboard API functionality over a local intranet without a public domain name?
- I use a local server application with a http interface on my home Intranet, accessed via FireFox (a web browser). I do not want the program to be accessed from the internet, and don't have and don't think I want a public domain for my local Intranet server. In the past I have been accessing it from Firefox by book marking the IP address and port.
- The program has recently changed from using Document.execCommand() method to the modern asynchronous Clipboard API.
- The clipboard API in Firefox defaults to requiring the host is accessed via https (appropriate for public facing internet access) or the host server is run on the same machine as the web browser (127.0.0.1 or localhost).
- From a security perspective I'm not convinced I need encryption between computer in my home networks (if that traffic is being intercepted to spy on or modify my clipboard, then my private network has already been severely compromised).
As a result of the clipboard API conventions, the program's clipboard functionality no longer works for me. I have tried
- looking for a Firefox exception settings, to enable clipboard API functionally over http (vs https) for specific local IP, but could not find how to do that in FireFox
- I have tried installing Caddy but without a domain name I couldn't get it to reverse-proxy to https
Am I missing an easy solution or do local servers need public addresses now.
Patch1 மூலமாக திருத்தப்பட்டது
தீர்வு தேர்ந்தெடுக்கப்பட்டது
To answer my own questin, the problem was my knowledge of caddy configuration.
In more detail, for a local server with a local IP address of for example 192.168.1.10 on port 8080.
This caddyfile does not allow https access on port 8081 from local intranet computers (only "localhost" on the server computer works)
:8081 reverse_proxy 127.0.0.1:8080
But this caddyfile allows access from the server computer or local intranet computers, and port 80 redirecting to port 443
192.168.1.10, localhost, 127.0.0.1 reverse_proxy 127.0.0.1:8080
Read this answer in context 👍 0All Replies (1)
தீர்வு தேர்ந்தெடுக்கப்பட்டது
To answer my own questin, the problem was my knowledge of caddy configuration.
In more detail, for a local server with a local IP address of for example 192.168.1.10 on port 8080.
This caddyfile does not allow https access on port 8081 from local intranet computers (only "localhost" on the server computer works)
:8081 reverse_proxy 127.0.0.1:8080
But this caddyfile allows access from the server computer or local intranet computers, and port 80 redirecting to port 443
192.168.1.10, localhost, 127.0.0.1 reverse_proxy 127.0.0.1:8080