aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2018-07-09 23:57:44 +0200
committerDaniel Stenberg <daniel@haxx.se>2018-07-10 10:08:07 +0200
commit522236f55eea7a15571317bd6fcccc4abff8fe8c (patch)
treeb7c04150b324149dadbe94afca791c582f10c77f /docs
parente0a4bba730671c4336cec9c2000844eedfaac9a6 (diff)
post303.d: clarify that this is an RFC violation
... and not the other way around, which this previously said. Reported-by: Vasiliy Faronov Fixes #2723 Closes #2726
Diffstat (limited to 'docs')
-rw-r--r--docs/cmdline-opts/post303.d9
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/cmdline-opts/post303.d b/docs/cmdline-opts/post303.d
index f8a60ec5f..44f39e610 100644
--- a/docs/cmdline-opts/post303.d
+++ b/docs/cmdline-opts/post303.d
@@ -4,8 +4,7 @@ Protocols: HTTP
See-also: post302 post301 location
Added: 7.26.0
---
-Tells curl to respect RFC 7231/6.4.4 and not convert POST requests into GET
-requests when following a 303 redirection. The non-RFC behaviour is ubiquitous
-in web browsers, so curl does the conversion by default to maintain
-consistency. However, a server may require a POST to remain a POST after such
-a redirection. This option is meaningful only when using --location.
+Tells curl to violate RFC 7231/6.4.4 and not convert POST requests into GET
+requests when following 303 redirections. A server may require a POST to
+remain a POST after a 303 redirection. This option is meaningful only when
+using --location.