You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an option to hide the port and colon in the displayed QRCode, or
Allow users to specify a full base URL. This option must conflict with --fqdn and --port option, and could even let users specify the protocol (example: -f https://qrcp.example.com.
Advantages:
Cleaner URL;
Allows HTTPS if the reverse proxy handle certificate generation (like Caddy);
Allows people behind high-restricted proxy (not allowing users to access websites that are not on port 80 or 443), to use qrcp;
Using a custom DNS + reverse proxy like presented, allows the use of qrcp behind NATed network (qrcd server is in a NATed network, reverse proxy is on the edge of the network or on a remote server forwarding traffic through SSH tunnel, and user is on a different network like 4G).
The text was updated successfully, but these errors were encountered:
Hi, thanks for suggesting, I like this a lot. Let me think about a couple possible implementation and will let you know.
It may take some days, I'm a bit busy lately.
I like the second approach the most, honestly. However, we will have to figure out how not to confuse the end user about what is used and what is just displayed.
I'm opening this issue because:
Feature proposal:
Add an option allowing users to hide the port (and the colon) displayed in the QRCode and URL, allowing people to put qrcp behind a reverse proxy.
Problem example:
Proposal:
--fqdn
and--port
option, and could even let users specify the protocol (example:-f https://qrcp.example.com
.Advantages:
The text was updated successfully, but these errors were encountered: