QuickShare over HTTPS
What HTTPS unlocks, why your browser shows a warning — and when it’s worth the extra step.
Why does this option exist?
QuickShare runs as a small web server on your PC. Other devices on the same network open the web interface in their browser. Browsers gate certain features — for example, copying images directly to the clipboard via the Clipboard API — to a so-called secure context. That means: only over HTTPS or via localhost. Over a LAN IP on plain HTTP, this feature is unavailable.
Why does the browser show a warning?
For HTTPS to work, the server needs a certificate. QuickShare generates this certificate itself and stores it locally on your PC. It is not signed by a public certificate authority — for a LAN application, that would be neither necessary nor possible. Browsers therefore mark such connections as “not trusted”. You confirm the warning once per device (“Advanced” → “Continue anyway”) and the browser remembers the exception.
What it looks like in the browser
On first connect, every browser shows a one-time security warning per device. Here’s where to click, step by step — the browser then remembers the exception.
Chrome (Desktop)
Step 1 — Click Advanced
On the first call of the HTTPS URL this warning appears. Click Advanced at the bottom to reveal the additional options.
Step 2 — Click Continue to … (unsafe)
Now the link appears that lets you connect anyway. The browser remembers the exception for this device — you won’t see the warning the next time you connect.
Edge (Desktop)
Step 1 — Click Advanced
On the first call of the HTTPS URL this warning appears. Click Advanced at the bottom to reveal the additional options.
Step 2 — Click Continue to … (unsafe)
Now the link appears that lets you connect anyway. The browser remembers the exception for this device — you won’t see the warning the next time you connect.
Safari (iOS)
Step 1 — Click Advanced
On the first call of the HTTPS URL this warning appears. Click Advanced at the bottom to reveal the additional options.
Step 2 — Click Continue to … (unsafe)
Now the link appears that lets you connect anyway. The browser remembers the exception for this device — you won’t see the warning the next time you connect.
HTTP or HTTPS — which one should you pick?
Both protocols make sense — depending on what you do most often:
HTTP (default)
No browser warning. Sharing text and files works completely. Images can be copied via right-click → Copy image, or downloaded — only the one-click copy-to-clipboard button is unavailable.
HTTPS
One-time security notice per device, after which everything works — including direct image copying to the clipboard via the copy button.
How do I switch?
Open the Cortility configuration and choose either HTTP or HTTPS in the QuickShare section under Protocol. The QuickShare service restarts automatically when you switch. The first time you open the HTTPS URL on a device, you’ll see the security notice — just choose “Advanced” and “Continue anyway”.
Is HTTPS with a self-signed certificate even secure?
The connection between your browser and QuickShare is encrypted — the self-signed certificate doesn’t change that. What the warning actually says is: the browser cannot confirm the server’s identity through a public certificate authority. Inside your own Wi-Fi, where QuickShare runs on your own PC, that’s fine — you know which device you’re connected to. For public-facing websites, a certificate like this would obviously be unsuitable.