summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMårten Nordheim <marten.nordheim@qt.io>2022-01-14 12:51:40 +0100
committerMårten Nordheim <marten.nordheim@qt.io>2022-01-18 18:43:55 +0000
commit7e82cefb728df14e889334dcf26f13fd8a616a14 (patch)
tree4d15a8fb3973c05565a6a659095dd5d24c4f2725
parent5180e70dbeb262edc2651f3b03e3f9d1cdf20729 (diff)
QNetworkRequest: Document how Qt handles 301 and 302 status codes
To make it explicit Pick-to: 6.3 6.2 5.15 Task-number: QTBUG-92909 Change-Id: I8f8dc99628168a566158acef72ae2a5e001eef88 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>
-rw-r--r--src/network/access/qnetworkrequest.cpp5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/network/access/qnetworkrequest.cpp b/src/network/access/qnetworkrequest.cpp
index de40b2c088..8cc916b153 100644
--- a/src/network/access/qnetworkrequest.cpp
+++ b/src/network/access/qnetworkrequest.cpp
@@ -410,6 +410,11 @@ QT_BEGIN_NAMESPACE
for example, to ask the user whether to
accept the redirect, or to decide
based on some app-specific configuration.
+
+ \note When Qt handles redirects it will, for legacy and compatibility
+ reasons, issue the redirected request using GET when the server returns
+ a 301 or 302 response, regardless of the original method used, unless it was
+ HEAD.
*/
/*!