network: Fix typos in documentation
Pick-to: 5.15 6.2 Change-Id: I386c6e4a21dacb2553a39a073052dcf6d92a9854 Reviewed-by: Giuseppe D'Angelo <giuseppe.dangelo@kdab.com> Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>bb10
parent
5f01d33dbf
commit
72c7c96143
|
|
@ -159,7 +159,7 @@ QHttp2Configuration::~QHttp2Configuration()
|
|||
|
||||
/*!
|
||||
If \a enable is \c true, a remote server can potentially
|
||||
use server push to send reponses in advance.
|
||||
use server push to send responses in advance.
|
||||
|
||||
\sa serverPushEnabled
|
||||
*/
|
||||
|
|
|
|||
|
|
@ -685,7 +685,7 @@ bool QNetworkAccessManager::isStrictTransportSecurityEnabled() const
|
|||
store is enabled, these policies will be preserved in the store. In case both
|
||||
cache and store contain the same known hosts, policies from cache are considered
|
||||
to be more up-to-date (and thus will overwrite the previous values in the store).
|
||||
If this behavior is undesired, enable HSTS store before enabling Strict Tranport
|
||||
If this behavior is undesired, enable HSTS store before enabling Strict Transport
|
||||
Security. By default, the persistent store of HSTS policies is disabled.
|
||||
|
||||
\sa isStrictTransportSecurityStoreEnabled(), setStrictTransportSecurityEnabled(),
|
||||
|
|
|
|||
|
|
@ -43,9 +43,9 @@
|
|||
|
||||
\section1 API changes
|
||||
|
||||
\section2 Ambigous name overloads
|
||||
\section2 Ambiguous name overloads
|
||||
|
||||
Several ambigous overloaded functions are removed. The error() signal
|
||||
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:
|
||||
|
|
|
|||
|
|
@ -492,7 +492,7 @@ void QNetworkAddressEntry::clearAddressLifetime()
|
|||
\since 5.11
|
||||
|
||||
Returns \c true if this address is permanent on this interface, \c false if
|
||||
it's temporary. A permenant address is one which has no expiration time and
|
||||
it's temporary. A permanent address is one which has no expiration time and
|
||||
is often static (manually configured).
|
||||
|
||||
If this information could not be determined, this function returns \c true.
|
||||
|
|
|
|||
|
|
@ -189,7 +189,7 @@
|
|||
|
||||
QNetworkProxy sets different capabilities by default when the
|
||||
object is created (see QNetworkProxy::ProxyType for a list of the
|
||||
defaults). However, it is possible to change the capabitilies
|
||||
defaults). However, it is possible to change the capabilities
|
||||
after the object has been created with setCapabilities().
|
||||
|
||||
The capabilities that QNetworkProxy supports are:
|
||||
|
|
|
|||
|
|
@ -430,7 +430,7 @@
|
|||
|
||||
\value DontShareAddress Bind the address and port exclusively, so that
|
||||
no other services are allowed to rebind. By passing this option to
|
||||
QAbstractSocket::bind(), you are guaranteed that on successs, your service
|
||||
QAbstractSocket::bind(), you are guaranteed that on success, your service
|
||||
is the only one that listens to the address and port. No services are
|
||||
allowed to rebind, even if they pass ReuseAddressHint. This option
|
||||
provides more security than ShareAddress, but on certain operating
|
||||
|
|
|
|||
|
|
@ -154,7 +154,7 @@ QLocalServer::~QLocalServer()
|
|||
In some cases, such as with Unix domain sockets on Linux, the
|
||||
access to the socket will be determined by file system permissions,
|
||||
and are created based on the umask. Setting the access flags will
|
||||
overide this and will restrict or permit access as specified.
|
||||
override this and will restrict or permit access as specified.
|
||||
|
||||
Other Unix-based operating systems, such as \macos, do not
|
||||
honor file permissions for Unix domain sockets and by default
|
||||
|
|
|
|||
|
|
@ -105,7 +105,7 @@ QT_BEGIN_NAMESPACE
|
|||
Note that unlike in most other QIODevice subclasses, open() may not open the device directly.
|
||||
The function return false if the socket was already connected or if the server to connect
|
||||
to was not defined and true in any other case. The connected() or errorOccurred() signals will be
|
||||
emitted once the device is actualy open (or the connection failed).
|
||||
emitted once the device is actually open (or the connection failed).
|
||||
|
||||
See connectToServer() for more details.
|
||||
*/
|
||||
|
|
|
|||
|
|
@ -899,7 +899,7 @@ bool QDtls::startHandshake(QUdpSocket *socket, const QByteArray &datagram)
|
|||
}
|
||||
|
||||
/*!
|
||||
If a timeout occures during the handshake, the handshakeTimeout() signal
|
||||
If a timeout occurs during the handshake, the handshakeTimeout() signal
|
||||
is emitted. The application must call handleTimeout() to retransmit handshake
|
||||
messages; handleTimeout() returns \c true if a timeout has occurred, false
|
||||
otherwise. \a socket must be a valid pointer.
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ QT_BEGIN_NAMESPACE
|
|||
\ingroup ssl
|
||||
\inmodule QtNetwork
|
||||
|
||||
The QOcspResponse class represents the revocation status of a server's certficate,
|
||||
The QOcspResponse class represents the revocation status of a server's certificate,
|
||||
received by the client-side socket during the TLS handshake. QSslSocket must be
|
||||
configured with OCSP stapling enabled.
|
||||
|
||||
|
|
|
|||
|
|
@ -188,7 +188,7 @@
|
|||
behavior is identical to QTcpSocket.
|
||||
|
||||
\value SslClientMode The socket is a client-side SSL socket.
|
||||
It is either alreayd encrypted, or it is in the SSL handshake
|
||||
It is either already encrypted, or it is in the SSL handshake
|
||||
phase (see QSslSocket::isEncrypted()).
|
||||
|
||||
\value SslServerMode The socket is a server-side SSL socket.
|
||||
|
|
|
|||
|
|
@ -1507,7 +1507,7 @@ QByteArray TlsKey::pemFooter() const
|
|||
\fn QStringList X509Certificate::issuerInfo(const QByteArray &attribute) const
|
||||
\internal
|
||||
|
||||
This function is excpected to return the issuer information for attribute from
|
||||
This function is expected to return the issuer information for attribute from
|
||||
the certificate, or an empty list if there is no information for \a attribute
|
||||
in the certificate. There can be more than one entry for an attribute.
|
||||
|
||||
|
|
@ -1842,7 +1842,7 @@ TlsKey *X509Certificate::publicKey() const
|
|||
the handshake.
|
||||
|
||||
\note This function is responsible for emitting QSslSocket's signals, that occur during the
|
||||
handshake (e.g. QSslSocket::sslErrors() or QSslSocket::encrytped()), and also read/write signals,
|
||||
handshake (e.g. QSslSocket::sslErrors() or QSslSocket::encrypted()), and also read/write signals,
|
||||
e.g. QSslSocket::bytesWritten() and QSslSocket::readyRead().
|
||||
|
||||
\sa init()
|
||||
|
|
@ -1938,7 +1938,7 @@ QList<QOcspResponse> TlsCryptograph::ocsps() const
|
|||
\internal
|
||||
|
||||
A helper function that can be used during a handshake. Returns \c true if the \a peerName
|
||||
matches one of subject alternative names or commond names found in the \a certificate.
|
||||
matches one of subject alternative names or common names found in the \a certificate.
|
||||
*/
|
||||
bool TlsCryptograph::isMatchingHostname(const QSslCertificate &certificate, const QString &peerName)
|
||||
{
|
||||
|
|
|
|||
Loading…
Reference in New Issue