- Joined
- Mar 17, 2022
A while ago I had to disable a "WebClient" service to make Outlook stop lagging when downloading attachments to a LAN drive by default.
For context, this "WebClient" service allowed PCs to share files with an http-using application I'd never heard of called WebDAV, and Outlook was trying this http method before defaulting to smb.
Serious question, no snark, etc. etc., but while I appreciate that Windows is at an advantage by supporting legacy shit, why is this legacy shit enabled by default, especially when it fucks up other, more modern applications? This seems like a prime candidate to be hidden behind an arcane reactivation process for whatever poor schmucks still need to use http-based file sharing (probably some Japanese company, IDK, I only know the stereotypes).
For context, this "WebClient" service allowed PCs to share files with an http-using application I'd never heard of called WebDAV, and Outlook was trying this http method before defaulting to smb.
Serious question, no snark, etc. etc., but while I appreciate that Windows is at an advantage by supporting legacy shit, why is this legacy shit enabled by default, especially when it fucks up other, more modern applications? This seems like a prime candidate to be hidden behind an arcane reactivation process for whatever poor schmucks still need to use http-based file sharing (probably some Japanese company, IDK, I only know the stereotypes).