Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add an option to dismiss the "insecure HTTP server" warning for accounts on trusted networks

Aperta
  • Qualcosa non va?
#4,420 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ios, swift
Ambito
authentication, mobile

Direzione di ricerca

Start by locating where the app displays the insecure HTTP server warning and how account settings are stored. Then trace the warning's account-specific state and review how the app presents confirmations. Done means an account can acknowledge the risk and suppress the warning while other HTTP accounts continue to see it; no files or tests are named in the issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.
Problem

Since a recent update, accounts using an http:// URL show a persistent banner: "This account uses an insecure HTTP server address. Data is transmitted without encryption."

The warning is useful by default, but it's a false positive when the connection is already encrypted below the application layer, and there's currently no way to acknowledge it.

My setup
  • Self-hosted Nextcloud on a NAS at http://192.168.x.x:30027, not exposed to the Internet.
  • Remote access is done exclusively through a WireGuard VPN tunnel to my home network.

Traffic is already encrypted by WireGuard, so adding HTTPS (domain, reverse proxy, local DNS, certificates) would add maintenance overhead for no real security gain. The app can't detect the tunnel, so the banner is always displayed.

Proposed solution

A per-account option to hide the warning (e.g. "I understand the risk" on the banner, or a toggle in account settings), with a confirmation dialog explaining the risks on first use. The warning stays enabled by default, and the choice is stored per account so new HTTP accounts still trigger it.

Alternatives considered
  • Switching to HTTPS with an internal domain and DNS-challenge certificates: disproportionate for a VPN-only setup.
  • Self-signed certificate / private CA: must be installed and trusted on every device.

Users on Tailscale, ZeroTier, or isolated local networks would likely benefit too.

  • App version:
  • iOS version:
  • Nextcloud server version:
Lingua principale
Swift
Stelle
2.5k
Fork
1k
Merge medio
1g 9h
PR unite (30g)
44

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/ios

Tutte le issue di nextcloud/ios

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.