[GNUnet-SVN] [gnurl] 156/163: post303.d: clarify that this is an RFC violation

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnurl.

commit 522236f55eea7a15571317bd6fcccc4abff8fe8c
Author: Daniel Stenberg <address@hidden>
AuthorDate: Mon Jul 9 23:57:44 2018 +0200

    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
---
 docs/cmdline-opts/post303.d | 9 ++++-----
 1 file 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.

-- 
To stop receiving notification emails like this one, please contact
address@hidden