QNetworkCookie#

The QNetworkCookie class holds one network cookie. More…

Synopsis#

Functions#

def domain ()
def expirationDate ()
def hasSameIdentifier (other)
def isHttpOnly ()
def isSecure ()
def isSessionCookie ()
def name ()
def normalize (url)
def __ne__ (other)
def __eq__ (other)
def path ()
def sameSitePolicy ()
def setDomain (domain)
def setExpirationDate (date)
def setHttpOnly (enable)
def setName (cookieName)
def setPath (path)
def setSameSitePolicy (sameSite)
def setSecure (enable)
def setValue (value)
def swap (other)
def toRawForm ([form=QNetworkCookie.RawForm.Full])
def value ()

Static functions#

def parseCookies (cookieString)

Note

This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE

Detailed Description#

Cookies are small bits of information that stateless protocols like HTTP use to maintain some persistent information across requests.

A cookie is set by a remote server when it replies to a request and it expects the same cookie to be sent back when further requests are sent.

QNetworkCookie holds one such cookie as received from the network. A cookie has a name and a value, but those are opaque to the application (that is, the information stored in them has no meaning to the application). A cookie has an associated path name and domain, which indicate when the cookie should be sent again to the server.

A cookie can also have an expiration date, indicating its validity. If the expiration date is not present, the cookie is considered a “session cookie” and should be discarded when the application exits (or when its concept of session is over).

QNetworkCookie provides a way of parsing a cookie from the HTTP header format using the parseCookies() function. However, when received in a QNetworkReply , the cookie is already parsed.

This class implements cookies as described by the initial cookie specification by Netscape , which is somewhat similar to the RFC 2109 specification, plus the “HttpOnly” extension . The more recent RFC 2965 specification (which uses the Set-Cookie2 header) is not supported.

See also

QNetworkCookieJar QNetworkRequest QNetworkReply

class PySide6.QtNetwork.QNetworkCookie([name=QByteArray()[, value=QByteArray()]])#

PySide6.QtNetwork.QNetworkCookie(other)

Parameters:

name – PySide6.QtCore.QByteArray
other – PySide6.QtNetwork.QNetworkCookie
value – PySide6.QtCore.QByteArray

Create a new QNetworkCookie object, initializing the cookie name to name and its value to value.

A cookie is only valid if it has a name. However, the value is opaque to the application and being empty may have significance to the remote server.

Creates a new QNetworkCookie object by copying the contents of other.

PySide6.QtNetwork.QNetworkCookie.RawForm#

This enum is used with the toRawForm() function to declare which form of a cookie shall be returned.

Constant

Description

QNetworkCookie.NameAndValueOnly

makes toRawForm() return only the “NAME=VALUE” part of the cookie, as suitable for sending back to a server in a client request’s “Cookie:” header. Multiple cookies are separated by a semi-colon in the “Cookie:” header field.

QNetworkCookie.Full

makes toRawForm() return the full cookie contents, as suitable for sending to a client in a server’s “Set-Cookie:” header.

Constant	Description
QNetworkCookie.NameAndValueOnly	makes `toRawForm()` return only the “NAME=VALUE” part of the cookie, as suitable for sending back to a server in a client request’s “Cookie:” header. Multiple cookies are separated by a semi-colon in the “Cookie:” header field.
QNetworkCookie.Full	makes `toRawForm()` return the full cookie contents, as suitable for sending to a client in a server’s “Set-Cookie:” header.

Note that only the Full form of the cookie can be parsed back into its original contents.

See also

toRawForm() parseCookies()

PySide6.QtNetwork.QNetworkCookie.SameSite#

Constant	Description
QNetworkCookie.SameSite.Default	SameSite is not set. Can be interpreted as None or Lax by the browser.
QNetworkCookie.SameSite.None	Cookies can be sent in all contexts. This used to be default, but recent browsers made Lax default, and will now require the cookie to be both secure and to set SameSite=None.
QNetworkCookie.SameSite.Lax	Cookies are sent on first party requests and GET requests initiated by third party website. This is the default in modern browsers (since mid 2020).
QNetworkCookie.SameSite.Strict	Cookies will only be sent in a first-party context.