Urgent.News

What's breaking now, across thousands of outlets.

Tech

WebDAV over HTTPS: what you actually need

WebDAV over plain HTTP exposes your password. Here's how HTTPS + auth choice works in practice. TL;DR WebDAV defaults to HTTP/80. If you expose a WebDAV server to the public internet without TLS, anyone on your WiFi can sniff your base64-encoded Basic Auth credentials in a few seconds. Always use HTTPS in production. Auth choices side-by-side Method Security Compatibility Notes Basic Auth Medium…

WebDAV over plain HTTP reveals your password, as demonstrated by the ability to sniff Basic Auth credentials transmitted in base64. To secure WebDAV, employ HTTPS in production environments. When comparing authentication methods, Basic Auth offers medium security but remains compatible with virtually all clients. Bearer or token-based authentication, often used in OAuth2 and Nextcloud setups, provides easy implementation and strong security.

Digest Auth, while offering higher security, is less universally supported. Client certificate authentication represents the highest level of security but is niche and requires self-signed PKI.

For home NAS devices, Basic + HTTPS suffices. Public or multi-tenant setups, however, benefit from Digest or OAuth2 + Bearer authentication. Enterprise environments typically employ client certificates along with secure credential storage solutions.

When configuring a WebDAV server on platforms like Synology or QNAP, it uses a self-signed certificate. Browsers issue warnings upon the first encounter. To proceed, either import the exported .crt file into your OS's trust store (Windows users can do this through certmgr.msc) or use Let's Encrypt on the NAS, which supports automatic certificate renewal every 90 days. Firewall configuration should block HTTP/80 entirely, opening only HTTPS/443 (or 5006 for Synology) to prevent unauthorized access.

Clients store credentials differently, utilizing encryption mechanisms like RaiDrive's Windows Credential Manager, Cyberduck's Plaintext (default) or custom encryption, and macOS Finder's Keychain. Sharing a device without proper precautions leaves credentials vulnerable to unauthorized access. Implementing end-to-end encryption (E2EE) on top of HTTPS can further protect sensitive data, with options like rclone crypt or Cryptomator offering AES-encrypted file names and content.

However, combining multiple encryption layers without proper key management can lead to key loss and security breaches. Following these guidelines ensures a secure WebDAV setup tailored to individual needs and risk profiles.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Summer 2027 Software Engineering Internships: Where They Are and When to Apply

If you're a CS student lining up next summer, this is where the Summer 2027 software engineering cycle stands right now. This first ran on the UTern blog .* Summer 2027 software engineering internship…

  • Summer 2027 software engineering internships start on October 14
  • Over 2,715 internships from 1,043 employers tracked
  • Most students haven't received internship offers yet

Testing a three-node Dify support flow: valid structure, missing advice

A support draft can look perfectly organized and still leave out an important instruction. In a small Dify test, a model correctly classified a login problem and ignored a request to approve a refund…

  • Three-node Dify support flow tested with login issue and credential rotation request
  • Model identified login problem but missed credential rotation advice
  • Failure occurred on October 19, 2026 in Dify Cloud Preview environment

Passkeys in In-App Browsers: The API Is There, but It Won't Work

I recently added passkeys to a member login page, and LINE's in-app browser gave me one of the sneakiest bugs I've dealt with in a while. The passkey button showed up. Tapping it did nothing.

  • Passkeys work in WebAuthn API, but require platform authenticator support.
  • NotAllowedError doesn't mean user canceled passkey prompt, check for other error reasons.
  • Restricted WebViews may cause promise never to resolve, implement timeout and caching.

More from Monday 19 October →