From 8d3f947df6bdf11d9a4e6b8cf7a41b812f84be30 Mon Sep 17 00:00:00 2001
From: Daniel Stenberg <daniel@haxx.se>
Date: Fri, 28 Feb 2025 16:29:13 +0100
Subject: [PATCH] fixup extend docs

---
 docs/libcurl/opts/CURLOPT_FOLLOWLOCATION.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/libcurl/opts/CURLOPT_FOLLOWLOCATION.md b/docs/libcurl/opts/CURLOPT_FOLLOWLOCATION.md
index c7449776b4..af54e17e13 100644
--- a/docs/libcurl/opts/CURLOPT_FOLLOWLOCATION.md
+++ b/docs/libcurl/opts/CURLOPT_FOLLOWLOCATION.md
@@ -88,6 +88,10 @@ change PUT etc - and therefore also not when libcurl issues a custom PUT. A
 303 response makes it switch to GET independently of the original method
 (except for HEAD).
 
+To control for which of the 301/302/303 status codes libcurl should *not*
+switch back to GET for when doing a custom POST, and instead keep the custom
+method, use CURLOPT_POSTREDIR(3).
+
 If you prefer a custom POST method to be reset to exactly the method `POST`,
 use CURLFOLLOW_FIRSTONLY instead.