From: Daniel Stenberg Date: Sat, 17 Dec 2016 23:42:36 +0000 (+0100) Subject: cmdline-opts/post30X.d: fix the RFC references X-Git-Tag: curl-7_52_0~19 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=6cce4dbf830;p=thirdparty%2Fcurl.git cmdline-opts/post30X.d: fix the RFC references --- diff --git a/docs/cmdline-opts/post301.d b/docs/cmdline-opts/post301.d index edcaf8755e..87a9fe7edc 100644 --- a/docs/cmdline-opts/post301.d +++ b/docs/cmdline-opts/post301.d @@ -4,7 +4,7 @@ Protocols: HTTP See-also: post302 post303 location Added: 7.17.1 --- -Tells curl to respect RFC 7230/6.4.2 and not convert POST requests into GET +Tells curl to respect RFC 7231/6.4.2 and not convert POST requests into GET requests when following a 301 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 diff --git a/docs/cmdline-opts/post302.d b/docs/cmdline-opts/post302.d index 6ea5f09bbb..caf0d87f18 100644 --- a/docs/cmdline-opts/post302.d +++ b/docs/cmdline-opts/post302.d @@ -4,7 +4,7 @@ Protocols: HTTP See-also: post301 post303 location Added: 7.19.1 --- -Tells curl to respect RFC 7230/6.4.2 and not convert POST requests into GET +Tells curl to respect RFC 7231/6.4.3 and not convert POST requests into GET requests when following a 302 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 diff --git a/docs/cmdline-opts/post303.d b/docs/cmdline-opts/post303.d index 8b36c8211e..f8a60ec5f4 100644 --- a/docs/cmdline-opts/post303.d +++ b/docs/cmdline-opts/post303.d @@ -4,7 +4,7 @@ Protocols: HTTP See-also: post302 post301 location Added: 7.26.0 --- -Tells curl to respect RFC 7230/6.4.2 and not convert POST requests into GET +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