Version v1.71.2

docs/content/changelog.md

@@ -6,6 +6,29 @@ description: "Rclone Changelog"
 
 # Changelog
 
+## v1.71.2 - 2025-10-20
+
+[See commits](https://github.com/rclone/rclone/compare/v1.71.1...v1.71.2)
+
+- Bug Fixes
+  - build
+    - update Go to 1.25.3
+    - Update Docker image Alpine version to fix CVE-2025-9230
+  - bisync: Fix race when CaptureOutput is used concurrently (Nick Craig-Wood)
+  - doc fixes (albertony, dougal, iTrooz, Matt LaPaglia, Nick Craig-Wood)
+  - index: Add missing providers (dougal)
+  - serve http: Fix: logging URL on start (dougal)
+- Azurefiles
+  - Fix server side copy not waiting for completion (Vikas Bhansali)
+- B2
+  - Fix 1TB+ uploads (dougal)
+- Google Cloud Storage
+  - Add region us-east5 (Dulani Woods)
+- Mega
+  - Fix 402 payment required errors (Nick Craig-Wood)
+- Pikpak
+  - Fix unnecessary retries by using URL expire parameter (Youfu Zhang)
+
 ## v1.71.1 - 2025-09-24
 
 [See commits](https://github.com/rclone/rclone/compare/v1.71.0...v1.71.1)

docs/content/commands/rclone.md

@@ -1013,7 +1013,7 @@ rclone [flags]
       --use-json-log                                        Use json log format
       --use-mmap                                            Use mmap allocator (see docs)
       --use-server-modtime                                  Use server modified time instead of object metadata
-      --user-agent string                                   Set the user-agent to a specified string (default "rclone/v1.71.1")
+      --user-agent string                                   Set the user-agent to a specified string (default "rclone/v1.71.2")
   -v, --verbose count                                       Print lots more stuff (repeat for more)
   -V, --version                                             Print the version number
       --webdav-auth-redirect                                Preserve authentication on redirect

docs/content/commands/rclone_authorize.md

@@ -11,12 +11,12 @@ Remote authorization.
 ## Synopsis
 
 Remote authorization. Used to authorize a remote or headless
-rclone from a machine with a browser - use as instructed by
-rclone config.
+rclone from a machine with a browser. Use as instructed by rclone config.
+See also the [remote setup documentation](/remote_setup).
 
 The command requires 1-3 arguments:
 
-- fs name (e.g., "drive", "s3", etc.)
+- Name of a backend (e.g. "drive", "s3")
 - Either a base64 encoded JSON blob obtained from a previous rclone config session
 - Or a client_id and client_secret pair obtained from the remote service
 
@@ -27,7 +27,7 @@ Use --template to generate HTML output via a custom Go template. If a blank
 string is provided as an argument to this flag, the default template is used.
 
 ```
-rclone authorize <fs name> [base64_json_blob | client_id client_secret] [flags]
+rclone authorize <backendname> [base64_json_blob | client_id client_secret] [flags]
 ```
 
 ## Options

docs/content/commands/rclone_convmv.md

@@ -231,12 +231,12 @@ rclone convmv "stories/The Quick Brown Fox!.txt" --name-transform "all,command=e
 
 ```sh
 rclone convmv "stories/The Quick Brown Fox!" --name-transform "date=-{YYYYMMDD}"
-// Output: stories/The Quick Brown Fox!-20250924
+// Output: stories/The Quick Brown Fox!-20251020
 ```
 
 ```sh
 rclone convmv "stories/The Quick Brown Fox!" --name-transform "date=-{macfriendlytime}"
-// Output: stories/The Quick Brown Fox!-2025-09-24 0413PM
+// Output: stories/The Quick Brown Fox!-2025-10-20 1251PM
 ```
 
 ```sh

docs/content/commands/rclone_rcd.md

@@ -130,7 +130,7 @@ You can either use an htpasswd file which can take lots of users, or
 set a single username and password with the `--rc-user` and `--rc-pass` flags.
 
 Alternatively, you can have the reverse proxy manage authentication and use the
-username provided in the configured header with `--user-from-header`  (e.g., `--rc---user-from-header=x-remote-user`).
+username provided in the configured header with `--user-from-header`  (e.g., `--rc-user-from-header=x-remote-user`).
 Ensure the proxy is trusted and headers cannot be spoofed, as misconfiguration
 may lead to unauthorized access.
 

docs/content/commands/rclone_serve_http.md

@@ -132,7 +132,7 @@ You can either use an htpasswd file which can take lots of users, or
 set a single username and password with the `--user` and `--pass` flags.
 
 Alternatively, you can have the reverse proxy manage authentication and use the
-username provided in the configured header with `--user-from-header`  (e.g., `----user-from-header=x-remote-user`).
+username provided in the configured header with `--user-from-header`  (e.g., `--user-from-header=x-remote-user`).
 Ensure the proxy is trusted and headers cannot be spoofed, as misconfiguration
 may lead to unauthorized access.
 

docs/content/commands/rclone_serve_restic.md

@@ -173,7 +173,7 @@ You can either use an htpasswd file which can take lots of users, or
 set a single username and password with the `--user` and `--pass` flags.
 
 Alternatively, you can have the reverse proxy manage authentication and use the
-username provided in the configured header with `--user-from-header`  (e.g., `----user-from-header=x-remote-user`).
+username provided in the configured header with `--user-from-header`  (e.g., `--user-from-header=x-remote-user`).
 Ensure the proxy is trusted and headers cannot be spoofed, as misconfiguration
 may lead to unauthorized access.
 

docs/content/commands/rclone_serve_s3.md

@@ -155,7 +155,7 @@ You can either use an htpasswd file which can take lots of users, or
 set a single username and password with the `--user` and `--pass` flags.
 
 Alternatively, you can have the reverse proxy manage authentication and use the
-username provided in the configured header with `--user-from-header`  (e.g., `----user-from-header=x-remote-user`).
+username provided in the configured header with `--user-from-header`  (e.g., `--user-from-header=x-remote-user`).
 Ensure the proxy is trusted and headers cannot be spoofed, as misconfiguration
 may lead to unauthorized access.
 

docs/content/commands/rclone_serve_webdav.md

@@ -189,7 +189,7 @@ You can either use an htpasswd file which can take lots of users, or
 set a single username and password with the `--user` and `--pass` flags.
 
 Alternatively, you can have the reverse proxy manage authentication and use the
-username provided in the configured header with `--user-from-header`  (e.g., `----user-from-header=x-remote-user`).
+username provided in the configured header with `--user-from-header`  (e.g., `--user-from-header=x-remote-user`).
 Ensure the proxy is trusted and headers cannot be spoofed, as misconfiguration
 may lead to unauthorized access.
 

docs/content/flags.md

@@ -121,7 +121,7 @@ Flags for general networking and HTTP stuff.
       --tpslimit float                     Limit HTTP transactions per second to this
       --tpslimit-burst int                 Max burst of transactions for --tpslimit (default 1)
       --use-cookies                        Enable session cookiejar
-      --user-agent string                  Set the user-agent to a specified string (default "rclone/v1.71.1")
+      --user-agent string                  Set the user-agent to a specified string (default "rclone/v1.71.2")
 ```
 
 

docs/content/googlecloudstorage.md

@@ -595,6 +595,8 @@ Properties:
         - South Carolina
     - "us-east4"
         - Northern Virginia
+    - "us-east5"
+        - Ohio
     - "us-west1"
         - Oregon
     - "us-west2"