diff options
| author | Mate Barany <[email protected]> | 2024-06-24 15:05:38 +0200 |
|---|---|---|
| committer | Mate Barany <[email protected]> | 2024-06-25 17:13:19 +0200 |
| commit | 22f67be5f218beaacb53e5ab6cfaac092d73f714 (patch) | |
| tree | ed5a55ad1d0f8d0c98d90401fbca622715a0eb0c | |
| parent | 704362f3dd06798c8c33ce48aa6c71fa3ac4624f (diff) | |
Add a note to QNAM that RFC 2616 8.2.2. is not handled properly
Warn the user that we do not react to incoming data until we have
finished writing.
Task-number: QTBUG-114812
Change-Id: I533c23d0fbefd2accddd63bc9a3b384e2a5899b0
Reviewed-by: Paul Wicking <[email protected]>
| -rw-r--r-- | src/network/access/qnetworkaccessmanager.cpp | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/src/network/access/qnetworkaccessmanager.cpp b/src/network/access/qnetworkaccessmanager.cpp index b371730c3c2..610491e5709 100644 --- a/src/network/access/qnetworkaccessmanager.cpp +++ b/src/network/access/qnetworkaccessmanager.cpp @@ -205,6 +205,11 @@ static void ensureInitialized() Currently, for the HTTP protocol on desktop platforms, 6 requests are executed in parallel for one host/port combination. + \note QNetworkAccessManager doesn't handle RFC 2616 Section 8.2.2 properly, + in that it doesn't react to incoming data until it's done writing. For + example, the upload of a large file won't stop even if the server returns + a status code that instructs the client to not continue. + A more involved example, assuming the manager is already existent, can be: \snippet code/src_network_access_qnetworkaccessmanager.cpp 1 |