PythonQt.QtNetwork.QNetworkAccessManager · declarations 001
Back to PythonQt.QtNetwork.QNetworkAccessManager
Accessible
instance-attribute
Accessible: Any
CustomOperation
instance-attribute
CustomOperation: Any
DeleteOperation
instance-attribute
DeleteOperation: Any
GetOperation
instance-attribute
GetOperation: Any
HeadOperation
instance-attribute
HeadOperation: Any
NetworkAccessibility
instance-attribute
NetworkAccessibility: type
int([x]) -> integer int(x, base=10) -> integer
Convert a number or string to an integer, or return 0 if no arguments are given. If x is a number, return x.int(). For floating point numbers, this truncates towards zero.
If x is not a number or if base is given, then x must be a string, bytes, or bytearray instance representing an integer literal in the given base. The literal can be preceded by '+' or '-' and be surrounded by whitespace. The base defaults to 10. Valid bases are 0 and 2-36. Base 0 means to interpret the base from the string as an integer literal.
int('0b100', base=0) 4
NotAccessible
instance-attribute
NotAccessible: Any
Operation
instance-attribute
Operation: type
int([x]) -> integer int(x, base=10) -> integer
Convert a number or string to an integer, or return 0 if no arguments are given. If x is a number, return x.int(). For floating point numbers, this truncates towards zero.
If x is not a number or if base is given, then x must be a string, bytes, or bytearray instance representing an integer literal in the given base. The literal can be preceded by '+' or '-' and be surrounded by whitespace. The base defaults to 10. Valid bases are 0 and 2-36. Base 0 means to interpret the base from the string as an integer literal.
int('0b100', base=0) 4
PostOperation
instance-attribute
PostOperation: Any
PutOperation
instance-attribute
PutOperation: Any
UnknownAccessibility
instance-attribute
UnknownAccessibility: Any
UnknownOperation
instance-attribute
UnknownOperation: Any
activeConfiguration
activeConfiguration() -> Any
X.activeConfiguration() -> PythonQt.QtNetwork.QNetworkConfiguration
Upstream PySide2 reference signatures (binding differences may apply):
activeConfiguration(self) -> PySide2.QtNetwork.QNetworkConfiguration
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#activeConfiguration
authenticationRequired
authenticationRequired(*args: Any, **kwargs: Any) -> Any
Native PythonQt.QtNetwork.QNetworkAccessManager.authenticationRequired; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::authenticationRequired(QNetworkReply *reply, QAuthenticator *authenticator)
This signal is emitted whenever a final server requests authentication before it delivers the requested contents. The slot connected to this signal should fill the credentials for the contents (which can be determined by inspecting the reply object) in the authenticator object.
QNetworkAccessManager will cache the credentials internally and will send the same values if the server requires authentication again, without emitting the authenticationRequired() signal. If it rejects the credentials, this signal will be emitted again.
Note: To have the request not send credentials you must not call setUser() or setPassword() on the authenticator object. This will result in the finished() signal being emitted with a QNetworkReply with error AuthenticationRequiredError.
Note: It is not possible to use a QueuedConnection to connect to this signal, as the connection will fail if the authenticator has not been filled in with new information when the signal returns.
See also proxyAuthenticationRequired(), QAuthenticator::setUser(), and QAuthenticator::setPassword().
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#authenticationRequired
cache
cache() -> Any
X.cache() -> PythonQt.QtNetwork.QAbstractNetworkCache
Supplemental documentation: Qt 5 reference:
QAbstractNetworkCache *QNetworkAccessManager::cache() const
Returns the cache that is used to store data obtained from the network.
This function was introduced in Qt 4.5.
See also setCache().
Upstream PySide2 reference signatures (binding differences may apply):
cache(self) -> PySide2.QtNetwork.QAbstractNetworkCache
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#cache
clearAccessCache
clearAccessCache() -> None
X.clearAccessCache()
Supplemental documentation: Qt 5 reference:
void QNetworkAccessManager::clearAccessCache()
Flushes the internal cache of authentication data and network connections.
This function is useful for doing auto tests.
This function was introduced in Qt 5.0.
See also clearConnectionCache().
Upstream PySide2 reference signatures (binding differences may apply):
clearAccessCache(self) -> None
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#clearAccessCache
configuration
configuration() -> Any
X.configuration() -> PythonQt.QtNetwork.QNetworkConfiguration
Upstream PySide2 reference signatures (binding differences may apply):
configuration(self) -> PySide2.QtNetwork.QNetworkConfiguration
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#configuration
connectToHost
connectToHost(hostName: str, port: int) -> None
X.connectToHost(hostName, port)
Supplemental documentation: Qt 5 reference:
void QNetworkAccessManager::connectToHost(const QString \&hostName, quint16 port \= 80)
Initiates a connection to the host given by hostName at port port. This function is useful to complete the TCP handshake to a host before the HTTP request is made, resulting in a lower network latency.
Note: This function has no possibility to report errors.
This function was introduced in Qt 5.2.
See also connectToHostEncrypted(), get(), post(), put(), and deleteResource().
Upstream PySide2 reference signatures (binding differences may apply):
connectToHost(self, hostName: str, port: int=...) -> None
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#connectToHost
connectToHostEncrypted
connectToHostEncrypted(hostName: str, port: int, sslConfiguration: Any) -> None
X.connectToHostEncrypted(hostName, port, sslConfiguration)
Supplemental documentation: Qt 5 reference:
void QNetworkAccessManager::connectToHostEncrypted(const QString \&hostName, quint16 port \= 443, const QSslConfiguration \&sslConfiguration \= QSslConfiguration::defaultConfiguration())
Initiates a connection to the host given by hostName at port port, using sslConfiguration. This function is useful to complete the TCP and SSL handshake to a host before the HTTPS request is made, resulting in a lower network latency.
Note: Preconnecting a SPDY connection can be done by calling setAllowedNextProtocols() on sslConfiguration with QSslConfiguration::NextProtocolSpdy3_0 contained in the list of allowed protocols. When using SPDY, one single connection per host is enough, i.e. calling this method multiple times per host will not result in faster network transactions.
Note: This function has no possibility to report errors.
This function was introduced in Qt 5.2.
See also connectToHost(), get(), post(), put(), and deleteResource().
void QNetworkAccessManager::connectToHostEncrypted(const QString \&hostName, quint16 port, const QSslConfiguration \&sslConfiguration, const QString \&peerName)
This is an overloaded function.
Initiates a connection to the host given by hostName at port port, using sslConfiguration with peerName set to be the hostName used for certificate validation. This function is useful to complete the TCP and SSL handshake to a host before the HTTPS request is made, resulting in a lower network latency.
Note: Preconnecting a SPDY connection can be done by calling setAllowedNextProtocols() on sslConfiguration with QSslConfiguration::NextProtocolSpdy3_0 contained in the list of allowed protocols. When using SPDY, one single connection per host is enough, i.e. calling this method multiple times per host will not result in faster network transactions.
Note: This function has no possibility to report errors.
This function was introduced in Qt 5.13.
See also connectToHost(), get(), post(), put(), and deleteResource().
Upstream PySide2 reference signatures (binding differences may apply):
connectToHostEncrypted(self, hostName: str, port: int, sslConfiguration: PySide2.QtNetwork.QSslConfiguration, peerName: str) -> None
connectToHostEncrypted(self, hostName: str, port: int=..., sslConfiguration: PySide2.QtNetwork.QSslConfiguration=...) -> None
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#connectToHostEncrypted
cookieJar
cookieJar() -> Any
X.cookieJar() -> PythonQt.QtNetwork.QNetworkCookieJar
Supplemental documentation: Qt 5 reference:
QNetworkCookieJar *QNetworkAccessManager::cookieJar() const
Returns the QNetworkCookieJar that is used to store cookies obtained from the network as well as cookies that are about to be sent.
See also setCookieJar().
Upstream PySide2 reference signatures (binding differences may apply):
cookieJar(self) -> PySide2.QtNetwork.QNetworkCookieJar
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#cookieJar
createRequest
createRequest(op: Any, request: Any, outgoingData: Any) -> Any
X.createRequest(op, request, outgoingData) -> PythonQt.QtNetwork.QNetworkReply
Supplemental documentation: Qt 5 reference:
[virtual protected] QNetworkReply *QNetworkAccessManager::createRequest(QNetworkAccessManager::Operation op, const QNetworkRequest \&originalReq, QIODevice *outgoingData \= nullptr)
Returns a new QNetworkReply object to handle the operation op and request originalReq. The device outgoingData is always 0 for Get and Head requests, but is the value passed to post() and put() in those operations (the QByteArray variants will pass a QBuffer object).
The default implementation calls QNetworkCookieJar::cookiesForUrl() on the cookie jar set with setCookieJar() to obtain the cookies to be sent to the remote server.
The returned object must be in an open state.
Upstream PySide2 reference signatures (binding differences may apply):
createRequest(self, op: PySide2.QtNetwork.QNetworkAccessManager.Operation, request: PySide2.QtNetwork.QNetworkRequest, outgoingData: typing.Optional[PySide2.QtCore.QIODevice]=...) -> PySide2.QtNetwork.QNetworkReply
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#createRequest
deleteResource
deleteResource(request: Any) -> Any
X.deleteResource(request) -> PythonQt.QtNetwork.QNetworkReply
Supplemental documentation: Qt 5 reference:
QNetworkReply *QNetworkAccessManager::deleteResource(const QNetworkRequest \&request)
Sends a request to delete the resource identified by the URL of request.
Note: This feature is currently available for HTTP only, performing an HTTP DELETE request.
This function was introduced in Qt 4.6.
See also get(), post(), put(), and sendCustomRequest().
Upstream PySide2 reference signatures (binding differences may apply):
deleteResource(self, request: PySide2.QtNetwork.QNetworkRequest) -> PySide2.QtNetwork.QNetworkReply
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#deleteResource
destroyed
destroyed(*args: Any, **kwargs: Any) -> Any
Native PythonQt.QtNetwork.QNetworkAccessManager.destroyed; argument details are not documented.
encrypted
encrypted(*args: Any, **kwargs: Any) -> Any
Native PythonQt.QtNetwork.QNetworkAccessManager.encrypted; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::encrypted(QNetworkReply *reply)
This signal is emitted when an SSL/TLS session has successfully completed the initial handshake. At this point, no user data has been transmitted. The signal can be used to perform additional checks on the certificate chain, for example to notify users when the certificate for a website has changed. The reply parameter specifies which network reply is responsible. If the reply does not match the expected criteria then it should be aborted by calling QNetworkReply::abort() by a slot connected to this signal. The SSL configuration in use can be inspected using the QNetworkReply::sslConfiguration() method.
Internally, QNetworkAccessManager may open multiple connections to a server, in order to allow it process requests in parallel. These connections may be reused, which means that the encrypted() signal would not be emitted. This means that you are only guaranteed to receive this signal for the first connection to a site in the lifespan of the QNetworkAccessManager.
This function was introduced in Qt 5.1.
See also QSslSocket::encrypted() and QNetworkReply::encrypted().
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#encrypted
finished
finished(*args: Any, **kwargs: Any) -> Any
Native PythonQt.QtNetwork.QNetworkAccessManager.finished; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::finished(QNetworkReply *reply)
This signal is emitted whenever a pending network reply is finished. The reply parameter will contain a pointer to the reply that has just finished. This signal is emitted in tandem with the QNetworkReply::finished() signal.
See QNetworkReply::finished() for information on the status that the object will be in.
Note: Do not delete the reply object in the slot connected to this signal. Use deleteLater().
See also QNetworkReply::finished() and QNetworkReply::error().
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#finished
get
get(request: Any) -> Any
X.get(request) -> PythonQt.QtNetwork.QNetworkReply
Supplemental documentation: Qt 5 reference:
QNetworkReply *QNetworkAccessManager::get(const QNetworkRequest \&request)
Posts a request to obtain the contents of the target request and returns a new QNetworkReply object opened for reading which emits the readyRead() signal whenever new data arrives.
The contents as well as associated headers will be downloaded.
See also post(), put(), deleteResource(), and sendCustomRequest().
Upstream PySide2 reference signatures (binding differences may apply):
get(self, request: PySide2.QtNetwork.QNetworkRequest) -> PySide2.QtNetwork.QNetworkReply
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#get
head
head(request: Any) -> Any
X.head(request) -> PythonQt.QtNetwork.QNetworkReply
Supplemental documentation: Qt 5 reference:
QNetworkReply *QNetworkAccessManager::head(const QNetworkRequest \&request)
Posts a request to obtain the network headers for request and returns a new QNetworkReply object which will contain such headers.
The function is named after the HTTP request associated (HEAD).
Upstream PySide2 reference signatures (binding differences may apply):
head(self, request: PySide2.QtNetwork.QNetworkRequest) -> PySide2.QtNetwork.QNetworkReply
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#head
networkAccessible
instance-attribute
networkAccessible: Any
networkAccessibleChanged
networkAccessibleChanged(*args: Any, **kwargs: Any) -> Any
Native PythonQt.QtNetwork.QNetworkAccessManager.networkAccessibleChanged; argument details are not documented.
networkSessionConnected
networkSessionConnected(*args: Any, **kwargs: Any) -> Any
Native PythonQt.QtNetwork.QNetworkAccessManager.networkSessionConnected; argument details are not documented.
objectNameChanged
objectNameChanged(*args: Any, **kwargs: Any) -> Any
Native PythonQt.QtNetwork.QNetworkAccessManager.objectNameChanged; argument details are not documented.
post
post(request: Any, multiPart: Any) -> Any
X.post(request, multiPart) -> PythonQt.QtNetwork.QNetworkReply
Supplemental documentation: Qt 5 reference:
QNetworkReply *QNetworkAccessManager::post(const QNetworkRequest \&request, QIODevice *data)
Sends an HTTP POST request to the destination specified by request and returns a new QNetworkReply object opened for reading that will contain the reply sent by the server. The contents of the data device will be uploaded to the server.
data must be open for reading and must remain valid until the finished() signal is emitted for this reply.
Note: Sending a POST request on protocols other than HTTP and HTTPS is undefined and will probably fail.
See also get(), put(), deleteResource(), and sendCustomRequest().
QNetworkReply *QNetworkAccessManager::post(const QNetworkRequest \&request, const QByteArray \&data)
This is an overloaded function.
Sends the contents of the data byte array to the destination specified by request.
QNetworkReply *QNetworkAccessManager::post(const QNetworkRequest \&request, QHttpMultiPart *multiPart)
This is an overloaded function.
Sends the contents of the multiPart message to the destination specified by request.
This can be used for sending MIME multipart messages over HTTP.
This function was introduced in Qt 4.8.
See also QHttpMultiPart, QHttpPart, and put().
Upstream PySide2 reference signatures (binding differences may apply):
post(self, request: PySide2.QtNetwork.QNetworkRequest, data: PySide2.QtCore.QByteArray) -> PySide2.QtNetwork.QNetworkReply
post(self, request: PySide2.QtNetwork.QNetworkRequest, data: PySide2.QtCore.QIODevice) -> PySide2.QtNetwork.QNetworkReply
post(self, request: PySide2.QtNetwork.QNetworkRequest, multiPart: PySide2.QtNetwork.QHttpMultiPart) -> PySide2.QtNetwork.QNetworkReply
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#post
preSharedKeyAuthenticationRequired
preSharedKeyAuthenticationRequired(*args: Any, **kwargs: Any) -> Any
Native PythonQt.QtNetwork.QNetworkAccessManager.preSharedKeyAuthenticationRequired; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::preSharedKeyAuthenticationRequired(QNetworkReply *reply, QSslPreSharedKeyAuthenticator *authenticator)
This signal is emitted if the SSL/TLS handshake negotiates a PSK ciphersuite, and therefore a PSK authentication is then required. The reply object is the QNetworkReply that is negotiating such ciphersuites.
When using PSK, the client must send to the server a valid identity and a valid pre shared key, in order for the SSL handshake to continue. Applications can provide this information in a slot connected to this signal, by filling in the passed authenticator object according to their needs.
Note: Ignoring this signal, or failing to provide the required credentials, will cause the handshake to fail, and therefore the connection to be aborted.
Note: The authenticator object is owned by the reply and must not be deleted by the application.
This function was introduced in Qt 5.5.
See also QSslPreSharedKeyAuthenticator.
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#preSharedKeyAuthenticationRequired
proxy
proxy() -> Any
X.proxy() -> PythonQt.QtNetwork.QNetworkProxy
Supplemental documentation: Qt 5 reference:
QNetworkProxy QNetworkAccessManager::proxy() const
Returns the QNetworkProxy that the requests sent using this QNetworkAccessManager object will use. The default value for the proxy is QNetworkProxy::DefaultProxy.
See also setProxy(), setProxyFactory(), and proxyAuthenticationRequired().
Upstream PySide2 reference signatures (binding differences may apply):
proxy(self) -> PySide2.QtNetwork.QNetworkProxy
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#proxy
proxyAuthenticationRequired
proxyAuthenticationRequired(*args: Any, **kwargs: Any) -> Any
Native PythonQt.QtNetwork.QNetworkAccessManager.proxyAuthenticationRequired; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QNetworkAccessManager::proxyAuthenticationRequired(const QNetworkProxy \&proxy, QAuthenticator *authenticator)
This signal is emitted whenever a proxy requests authentication and QNetworkAccessManager cannot find a valid, cached credential. The slot connected to this signal should fill in the credentials for the proxy proxy in the authenticator object.
QNetworkAccessManager will cache the credentials internally. The next time the proxy requests authentication, QNetworkAccessManager will automatically send the same credential without emitting the proxyAuthenticationRequired signal again.
If the proxy rejects the credentials, QNetworkAccessManager will emit the signal again.
See also proxy(), setProxy(), and authenticationRequired().
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#proxyAuthenticationRequired
proxyFactory
proxyFactory() -> Any
X.proxyFactory() -> PythonQt.QtNetwork.QNetworkProxyFactory
Supplemental documentation: Qt 5 reference:
QNetworkProxyFactory *QNetworkAccessManager::proxyFactory() const
Returns the proxy factory that this QNetworkAccessManager object is using to determine the proxies to be used for requests.
Note that the pointer returned by this function is managed by QNetworkAccessManager and could be deleted at any time.
This function was introduced in Qt 4.5.
See also setProxyFactory() and proxy().
Upstream PySide2 reference signatures (binding differences may apply):
proxyFactory(self) -> PySide2.QtNetwork.QNetworkProxyFactory
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#proxyFactory
put
put(request: Any, multiPart: Any) -> Any
X.put(request, multiPart) -> PythonQt.QtNetwork.QNetworkReply
Supplemental documentation: Qt 5 reference:
QNetworkReply *QNetworkAccessManager::put(const QNetworkRequest \&request, QIODevice *data)
Uploads the contents of data to the destination request and returns a new QNetworkReply object that will be open for reply.
data must be opened for reading when this function is called and must remain valid until the finished() signal is emitted for this reply.
Whether anything will be available for reading from the returned object is protocol dependent. For HTTP, the server may send a small HTML page indicating the upload was successful (or not). Other protocols will probably have content in their replies.
Note: For HTTP, this request will send a PUT request, which most servers do not allow. Form upload mechanisms, including that of uploading files through HTML forms, use the POST mechanism.
See also get(), post(), deleteResource(), and sendCustomRequest().
QNetworkReply *QNetworkAccessManager::put(const QNetworkRequest \&request, const QByteArray \&data)
This is an overloaded function.
Sends the contents of the data byte array to the destination specified by request.
QNetworkReply *QNetworkAccessManager::put(const QNetworkRequest \&request, QHttpMultiPart *multiPart)
This is an overloaded function.
Sends the contents of the multiPart message to the destination specified by request.
This can be used for sending MIME multipart messages over HTTP.
This function was introduced in Qt 4.8.
See also QHttpMultiPart, QHttpPart, and post().
Upstream PySide2 reference signatures (binding differences may apply):
put(self, request: PySide2.QtNetwork.QNetworkRequest, data: PySide2.QtCore.QByteArray) -> PySide2.QtNetwork.QNetworkReply
put(self, request: PySide2.QtNetwork.QNetworkRequest, data: PySide2.QtCore.QIODevice) -> PySide2.QtNetwork.QNetworkReply
put(self, request: PySide2.QtNetwork.QNetworkRequest, multiPart: PySide2.QtNetwork.QHttpMultiPart) -> PySide2.QtNetwork.QNetworkReply
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#put
sendCustomRequest
sendCustomRequest(request: Any, verb: Any, data: Any) -> Any
X.sendCustomRequest(request, verb, data) -> PythonQt.QtNetwork.QNetworkReply
Supplemental documentation: Qt 5 reference:
QNetworkReply *QNetworkAccessManager::sendCustomRequest(const QNetworkRequest \&request, const QByteArray \&verb, QIODevice *data \= nullptr)
Sends a custom request to the server identified by the URL of request.
It is the user's responsibility to send a verb to the server that is valid according to the HTTP specification.
This method provides means to send verbs other than the common ones provided via get() or post() etc., for instance sending an HTTP OPTIONS command.
If data is not empty, the contents of the data device will be uploaded to the server; in that case, data must be open for reading and must remain valid until the finished() signal is emitted for this reply.
Note: This feature is currently available for HTTP(S) only.
This function was introduced in Qt 4.7.
See also get(), post(), put(), and deleteResource().
QNetworkReply *QNetworkAccessManager::sendCustomRequest(const QNetworkRequest \&request, const QByteArray \&verb, const QByteArray \&data)
This is an overloaded function.
Sends the contents of the data byte array to the destination specified by request.
This function was introduced in Qt 5.8.
QNetworkReply *QNetworkAccessManager::sendCustomRequest(const QNetworkRequest \&request, const QByteArray \&verb, QHttpMultiPart *multiPart)
This is an overloaded function.
Sends a custom request to the server identified by the URL of request.
Sends the contents of the multiPart message to the destination specified by request.
This can be used for sending MIME multipart messages for custom verbs.
This function was introduced in Qt 5.8.
See also QHttpMultiPart, QHttpPart, and put().
Upstream PySide2 reference signatures (binding differences may apply):
sendCustomRequest(self, request: PySide2.QtNetwork.QNetworkRequest, verb: PySide2.QtCore.QByteArray, data: PySide2.QtCore.QByteArray) -> PySide2.QtNetwork.QNetworkReply
sendCustomRequest(self, request: PySide2.QtNetwork.QNetworkRequest, verb: PySide2.QtCore.QByteArray, data: typing.Optional[PySide2.QtCore.QIODevice]=...) -> PySide2.QtNetwork.QNetworkReply
sendCustomRequest(self, request: PySide2.QtNetwork.QNetworkRequest, verb: PySide2.QtCore.QByteArray, multiPart: PySide2.QtNetwork.QHttpMultiPart) -> PySide2.QtNetwork.QNetworkReply
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#sendCustomRequest
setCache
setCache(cache: Any) -> None
X.setCache(cache)
Supplemental documentation: Qt 5 reference:
void QNetworkAccessManager::setCache(QAbstractNetworkCache *cache)
Sets the manager's network cache to be the cache specified. The cache is used for all requests dispatched by the manager.
Use this function to set the network cache object to a class that implements additional features, like saving the cookies to permanent storage.
Note: QNetworkAccessManager takes ownership of the cache object.
QNetworkAccessManager by default does not have a set cache. Qt provides a simple disk cache, QNetworkDiskCache, which can be used.
This function was introduced in Qt 4.5.
See also cache() and QNetworkRequest::CacheLoadControl.
Upstream PySide2 reference signatures (binding differences may apply):
setCache(self, cache: PySide2.QtNetwork.QAbstractNetworkCache) -> None
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#setCache
setConfiguration
setConfiguration(config: Any) -> None
X.setConfiguration(config)
Upstream PySide2 reference signatures (binding differences may apply):
setConfiguration(self, config: PySide2.QtNetwork.QNetworkConfiguration) -> None
Source: https://doc.qt.io/archives/qt-5.15/qnetworkaccessmanager.html#setConfiguration