1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
|
// Copyright (C) 2020 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
/*!
\page network-changes-qt6.html
\title Changes to Qt Network
\ingroup changes-qt-5-to-6
\brief Migrate Qt Network to Qt 6.
Qt 6 is a result of the conscious effort to make the framework more
efficient and easy to use.
We try to maintain binary and source compatibility for all the public
APIs in each release. But some changes were inevitable in an effort to
make Qt a better framework.
In this topic we summarize those changes in Qt Network, and provide
guidance to handle them.
\section1 API changes
\section2 Ambiguous name overloads
Several ambiguous overloaded functions are removed. The error() signal
is replaced by errorOccurred() in QAbstractSocket and its heirs
(QTcpSocket, QUdpSocket, QLocalSocket, and QSslSocket), and in QNetworkReply.
Code such as:
\code
connect(socket, qOverload<QAbstractSocket::SocketError>(&QAbstractSocket::error),
this, &SomeClass::errorSlot);
\endcode
must therefore be changed to:
\code
connect(socket, &QAbstractSocket::errorOccurred, this, &SomeClass::errorSlot);
\endcode
In QSslSocket, the function that returns a list of errors encountered
during the TLS handshake:
\code
QList<QSslError> sslErrors() const;
\endcode
is renamed to sslHandshakeErrors():
\code
const auto tlsErrors = socket.sslHandshakeErrors();
\endcode
\section2 Bearer management is removed
The classes QNetworkConfiguration and QNetworkConfigurationManager are removed in Qt 6.
Consequently, the following member functions of QNetworkAccessManager are also removed:
\code
void setConfiguration(const QNetworkConfiguration &config);
QNetworkConfiguration configuration() const;
QNetworkConfiguration activeConfiguration() const;
void setNetworkAccessible(NetworkAccessibility accessible);
NetworkAccessibility networkAccessible() const;
void networkSessionConnected();
\endcode
QNetworkInformation, initially introduced in Qt 6.1, aims to replace some
aspects of the bearer management API. It works by providing a unified API
which subscribes to changes to the network as notified by the operating
system.
QNetworkInformation::reachability(), introduced in Qt 6.1, replaces the
QNetworkAccessManager::networkAccessible() function, while adding more
detailed information about the reachability of the network. See its
documentation for more details.
In Qt 6.2 QNetworkInformation gained the ability to detect captive portals.
In Qt 6.3 QNetworkInformation gained QNetworkInformation::transportMedium()
and QNetworkInformation::isMetered().
\section2 Deleted enumerators
Several enumerators are removed in QtNetwork. This includes constants
for no longer supported protocols and functionality:
\list
\li QSsl::SslV2;
\li QSsl::SslV3;
\li QSsl::TlsV1SslV3;
\li QNetworkRequest::SpdyAllowedAttribute;
\li QNetworkRequest::SpdyWasUsedAttribute;
\li QNetworkAccessManager::UnknownAccessibility;
\li QNetworkAccessManager::NotAccessible;
\li QNetworkAccessManager::Accessible
\endlist
and enumerators whose names did not follow proper naming conventions:
\list
\li QSsl::TlsV1 (QSsl::TlsV1_0 is the proper name);
\li QNetworkRequest::HTTP2AllowedAttribute (use QNetworkRequest::Http2AllowedAttribute);
\li QNetworkRequest::HTTP2WasUsedAttribute (use QNetworkRequest::Http2WasUsedAttribute).
\endlist
QNetworkRequest::FollowRedirectsAttribute is removed in Qt 6, see
\l {Redirect policies}{the section about redirects handling} below.
\section2 Configuring QSslSocket
The following deprecated functions are removed in Qt 6:
\code
QList<QSslCipher> ciphers() const;
void setCiphers(const QList<QSslCipher> &ciphers);
void setCiphers(const QString &ciphers);
static void setDefaultCiphers(const QList<QSslCipher> &ciphers);
static QList<QSslCipher> defaultCiphers();
static QList<QSslCipher> supportedCiphers();
QList<QSslCipher> ciphers() const;
void setCiphers(const QList<QSslCipher> &ciphers);
void setCiphers(const QString &ciphers);
static void setDefaultCiphers(const QList<QSslCipher> &ciphers);
static QList<QSslCipher> defaultCiphers();
static QList<QSslCipher> supportedCiphers();
bool addCaCertificates(const QString &path, QSsl::EncodingFormat format = QSsl::Pem,
QRegExp::PatternSyntax syntax = QRegExp::FixedString);
void addCaCertificate(const QSslCertificate &certificate);
void addCaCertificates(const QList<QSslCertificate> &certificates);
void setCaCertificates(const QList<QSslCertificate> &certificates);
QList<QSslCertificate> caCertificates() const;
static bool addDefaultCaCertificates(const QString &path, QSsl::EncodingFormat format = QSsl::Pem,
QRegExp::PatternSyntax syntax = QRegExp::FixedString);
static void addDefaultCaCertificate(const QSslCertificate &certificate);
static void addDefaultCaCertificates(const QList<QSslCertificate> &certificates);
static void setDefaultCaCertificates(const QList<QSslCertificate> &certificates);
static QList<QSslCertificate> defaultCaCertificates();
static QList<QSslCertificate> systemCaCertificates();
\endcode
Use QSslConfiguration and its member functions to set these parameters, e.g.:
\code
auto sslConfiguration = QSslConfiguration::defaultConfiguration();
sslConfiguration.setCiphers("ECDHE-ECDSA-AES256-SHA384");
// Set other parameters here ...
socket.setSslConfiguration(sslConfiguration);
\endcode
\section1 Changes in QNetworkAccessManager's default behavior
\section2 Redirect policies
In Qt 6, the default redirect policy has changed from manual to
QNetworkRequest::NoLessSafeRedirectPolicy. If your application relies
on manual redirect handling (it connects its slot to the QNetworkReply::redirected
signal), you have to explicitly set this policy when creating a request:
\code
request.setAttribute(QNetworkRequest::RedirectPolicyAttribute, QNetworkRequest::ManualRedirectPolicy);
\endcode
\section2 HTTP/2 is enabled by default
In Qt 6 QNetworkAccessManager enables HTTP/2 protocol by default. Depending on the
scheme ("https" or "http"), QNetworkAccessManager will use the Application Layer
Protocol Negotiation TLS extension or "protocol upgrade" HTTP header to negotiate HTTP/2.
If HTTP/2 cannot be negotiated, the access manager will fall back to using HTTP/1.1.
If your application can only use HTTP/1.1, you have to disable HTTP/2 manually
on a new request:
\code
request.setAttribute(QNetworkRequest::Http2AllowedAttribute, false);
\endcode
\section2 QNetworkAccessManager now guards against archive bombs
Starting with Qt 6.2 QNetworkAccessManager will guard against compressed
files that decompress to files which are much larger than their compressed
form by erroring out the reply if the decompression ratio exceeds a certain
threshold.
This check is only applied to files larger than a certain size, which can be
customized (or disabled by passing -1) by calling
\l{QNetworkRequest::setDecompressedSafetyCheckThreshold()}.
*/
|
