"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
Go azure-blobazure-blob-storageazure-filesbackblaze-b2cloud-storagedropboxencryptionftpfuse-filesystemgogolanggoogle-cloud-storagegoogle-driveonedriveopenstack-swiftrclones3sftpsyncwebdav
docs: explain Windows path escaping in the rc API
frodleTian90cd86b47b85
diff --git a/docs/content/rc.md b/docs/content/rc.mdindex 2aa685f9e..5fb5f62a5 100644--- a/docs/content/rc.md+++ b/docs/content/rc.md@@ -312,6 +312,30 @@ Rather thanrclone rc operations/list --json '{"fs": "/tmp", "remote": "test", "opt": {"showHash": true}}'```+### Paths on Windows++Prefer forward slashes (`/`) in Windows paths passed to the rc API, for+example `C:/path1/path2`. If you use backslashes (`\`) in a JSON string,+escape each one as `\\`. These JSON objects contain equivalent Windows+paths:++```json+{"remote": "C:/path1/path2"}+```++```json+{"remote": "C:\\path1\\path2"}+```++This applies to JSON request bodies and to JSON-encoded object parameters,+such as `parameters` in `config/create`, even when that JSON is sent in a+query string or form data. An unescaped backslash can cause a JSON parsing+error or be interpreted as an escape sequence, such as `\t` for a tab.++String parameters sent directly in a query string or form data, without+JSON encoding, do not need JSON escaping. Use your HTTP client's URL+encoding for query strings and form data.+## Special parametersThe rc interface supports some special parameters which apply to