QHttpMultiPart resembles a MIME multipart message, as described in RFC 2046, which is to be sent over HTTP. A multipart message consists of an arbitrary number of body parts (see
QHttpPart ), which are separated by a unique boundary. The boundary of the
QHttpMultiPart is constructed with the string “boundary_.oOo._” followed by random characters, and provides enough uniqueness to make sure it does not occur inside the parts itself. If desired, the boundary can still be set via
As an example, consider the following code snippet, which constructs a multipart message containing a text part followed by an image part:
multiPart = QHttpMultiPart(QHttpMultiPart.FormDataType) textPart = QHttpPart() textPart.setHeader(QNetworkRequest.ContentDispositionHeader, QVariant("form-data; name=\"text\"")) textPart.setBody("my text") imagePart = QHttpPart() imagePart.setHeader(QNetworkRequest.ContentTypeHeader, QVariant("image/jpeg")) imagePart.setHeader(QNetworkRequest.ContentDispositionHeader, QVariant("form-data; name=\"image\"")) file = QFile("image.jpg") file.open(QIODevice.ReadOnly) imagePart.setBodyDevice(file) file.setParent(multiPart) # we cannot delete the file now, so delete it with the multiPart multiPart.append(textPart) multiPart.append(imagePart) url = QUrl("http://my.server.tld") request = QNetworkRequest(url) manager = QNetworkAccessManager() reply = manager.post(request, multiPart) multiPart.setParent(reply) # delete the multiPart with the reply # here connect signals etc.
- class PySide6.QtNetwork.QHttpMultiPart(contentType[, parent=None])¶
QHttpMultiPart with content type
contentType and sets parent as the parent object.
QHttpMultiPart with content type
MixedType and sets
parent as the parent object.
List of known content types for a multipart subtype as described in RFC 2046 and others.
corresponds to the “multipart/mixed” subtype, meaning the body parts are independent of each other, as described in RFC 2046.
corresponds to the “multipart/related” subtype, meaning the body parts are related to each other, as described in RFC 2387.
corresponds to the “multipart/form-data” subtype, meaning the body parts contain form elements, as described in RFC 2388.
corresponds to the “multipart/alternative” subtype, meaning the body parts are alternative representations of the same information, as described in RFC 2046.
httpPart to this multipart.
returns the boundary.
Sets the boundary to
Usually, you do not need to generate a boundary yourself; upon construction the boundary is initiated with the string “boundary_.oOo._” followed by random characters, and provides enough uniqueness to make sure it does not occur inside the parts itself.
Sets the content type to
contentType. The content type will be used in the HTTP header section when sending the multipart message via
post() . In case you want to use a multipart subtype not contained in
ContentType , you can add the “Content-Type” header field to the
QNetworkRequest by hand, and then use this request together with the multipart message for posting.
© 2022 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.