summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2020-12-12 22:23:19 +0100
committerDaniel Stenberg <daniel@haxx.se>2020-12-12 22:23:19 +0100
commite4390ac3b810d25743b964a9b1b7433181714a25 (patch)
tree43185d550c988349510e5f727a0836dd00c76651
parent2a264d494e006b8ca9f1bad0798893c7b52f3a98 (diff)
downloadcurl-bagder/url-file-smb.tar.gz
URL-SYNTAX: mention how FILE:// access can access network on windowsbagder/url-file-smb
-rw-r--r--docs/URL-SYNTAX.md13
1 files changed, 10 insertions, 3 deletions
diff --git a/docs/URL-SYNTAX.md b/docs/URL-SYNTAX.md
index a7cd5a68d..8fd230113 100644
--- a/docs/URL-SYNTAX.md
+++ b/docs/URL-SYNTAX.md
@@ -200,9 +200,16 @@ curl only allows the hostname part of a FILE URL to be one out of these three
alternatives: `localhost`, `127.0.0.1` or blank ("", zero characters).
Anything else will make curl fail to parse the URL.
-On Windows, curl accepts that the FILE URL's path starts with a "drive
-letter". That's a single letter `a` to `z` followed by a colon or a pipe
-character (`|`).
+### Windows-specific FILE details
+
+curl accepts that the FILE URL's path starts with a "drive letter". That's a
+single letter `a` to `z` followed by a colon or a pipe character (`|`).
+
+The Windows operating system itself will convert some file accesses to perform
+network accesses over SMB/CIFS, through several different file path patterns.
+This way, a `file://` URL passed to curl *might* be converted into a network
+access inadvertently and unknowingly to curl. This is a Windows feature curl
+cannot control or disable.
## IMAP