Python Standard Library

Table of Contents

  • Ch 01 - 10
  • Ch 11 - 20
    • 11. Data Persistence
    • 12 Data Compression and Archiving
    • 13 File Formats
    • 14 Cryptographic Services
    • 15 Generic Operating System Services
    • 16 Optional Operating System Services
    • 17 Interprocess Communication and Networking
    • 18 Internet Data Handling
    • 19 Structured Markup Processing Tools
    • 20a Internet Protocols and Support
    • 20b Internet Protocols and Support
      • 1. telnetlib — Telnet client
      • 2. uuid — UUID objects according to RFC 4122
      • 3. urlparse — Parse URLs into components
      • 4. SocketServer — A framework for network servers
      • 5. BaseHTTPServer — Basic HTTP server
      • 6. SimpleHTTPServer — Simple HTTP request handler
      • 7. CGIHTTPServer — CGI-capable HTTP request handler
      • 8. cookielib — Cookie handling for HTTP clients
      • 9. Cookie — HTTP state management
        • 9.1. Cookie Objects
        • 9.2. Morsel Objects
        • 9.3. Example
      • 10. xmlrpclib — XML-RPC client access
      • 11. SimpleXMLRPCServer — Basic XML-RPC server
      • 12. DocXMLRPCServer — Self-documenting XML-RPC server
  • Ch 21 - 30
  • Ch 31 - 37
  • api
Python Standard Library
  • Docs »
  • Ch 11 - 20 »
  • 20b Internet Protocols and Support »
  • 9. Cookie — HTTP state management
  • View page source

9. Cookie — HTTP state management¶

Contents

  • Cookie Objects
  • Morsel Objects
  • Example

Note

The Cookie module has been renamed to http.cookies in Python 3. The 2to3 tool will automatically adapt imports when converting your sources to Python 3.

The Cookie module defines classes for abstracting the concept of cookies, an HTTP state management mechanism. It supports both simple string-only cookies, and provides an abstraction for having any serializable data-type as cookie value.

The module formerly strictly applied the parsing rules described in the RFC 2109 and RFC 2068 specifications. It has since been discovered that MSIE 3.0x doesn’t follow the character rules outlined in those specs and also many current day browsers and servers have relaxed parsing rules when comes to Cookie handling. As a result, the parsing rules used are a bit less strict.

The character set, string.ascii_letters, string.digits and !#$%&'*+-.^_`|~ denote the set of valid characters allowed by this module in Cookie name (as key).

Note

On encountering an invalid cookie, CookieError is raised, so if your cookie data comes from a browser you should always prepare for invalid data and catch CookieError on parsing.

exception Cookie.CookieError[source]¶

Exception failing because of RFC 2109 invalidity: incorrect attributes, incorrect Set-Cookie header, etc.

class Cookie.BaseCookie([input])[source]¶

This class is a dictionary-like object whose keys are strings and whose values are Morsel instances. Note that upon setting a key to a value, the value is first converted to a Morsel containing the key and the value.

If input is given, it is passed to the load() method.

class Cookie.SimpleCookie([input])[source]¶

This class derives from BaseCookie and overrides value_decode() and value_encode() to be the identity and str() respectively.

class Cookie.SerialCookie([input])[source]¶

This class derives from BaseCookie and overrides value_decode() and value_encode() to be the pickle.loads() and pickle.dumps().

Deprecated since version 2.3: Reading pickled values from untrusted cookie data is a huge security hole, as pickle strings can be crafted to cause arbitrary code to execute on your server. It is supported for backwards compatibility only, and may eventually go away.

class Cookie.SmartCookie([input])[source]¶

This class derives from BaseCookie. It overrides value_decode() to be pickle.loads() if it is a valid pickle, and otherwise the value itself. It overrides value_encode() to be pickle.dumps() unless it is a string, in which case it returns the value itself.

Deprecated since version 2.3: The same security warning from SerialCookie applies here.

A further security note is warranted. For backwards compatibility, the Cookie module exports a class named Cookie which is just an alias for SmartCookie. This is probably a mistake and will likely be removed in a future version. You should not use the Cookie class in your applications, for the same reason why you should not use the SerialCookie class.

See also

Module cookielib
HTTP cookie handling for web clients. The cookielib and Cookie modules do not depend on each other.
RFC 2109 - HTTP State Management Mechanism
This is the state management specification implemented by this module.

9.1. Cookie Objects¶

BaseCookie.value_decode(val)[source]¶

Return a decoded value from a string representation. Return value can be any type. This method does nothing in BaseCookie — it exists so it can be overridden.

BaseCookie.value_encode(val)[source]¶

Return an encoded value. val can be any type, but return value must be a string. This method does nothing in BaseCookie — it exists so it can be overridden.

In general, it should be the case that value_encode() and value_decode() are inverses on the range of value_decode.

BaseCookie.output([attrs[, header[, sep]]])[source]¶

Return a string representation suitable to be sent as HTTP headers. attrs and header are sent to each Morsel‘s output() method. sep is used to join the headers together, and is by default the combination '\r\n' (CRLF).

Changed in version 2.5: The default separator has been changed from '\n' to match the cookie specification.

BaseCookie.js_output([attrs])[source]¶

Return an embeddable JavaScript snippet, which, if run on a browser which supports JavaScript, will act the same as if the HTTP headers was sent.

The meaning for attrs is the same as in output().

BaseCookie.load(rawdata)[source]¶

If rawdata is a string, parse it as an HTTP_COOKIE and add the values found there as Morsels. If it is a dictionary, it is equivalent to:

for k, v in rawdata.items():
    cookie[k] = v

9.2. Morsel Objects¶

class Cookie.Morsel[source]¶

Abstract a key/value pair, which has some RFC 2109 attributes.

Morsels are dictionary-like objects, whose set of keys is constant — the valid RFC 2109 attributes, which are

  • expires
  • path
  • comment
  • domain
  • max-age
  • secure
  • version
  • httponly

The attribute httponly specifies that the cookie is only transferred in HTTP requests, and is not accessible through JavaScript. This is intended to mitigate some forms of cross-site scripting.

The keys are case-insensitive.

New in version 2.6: The httponly attribute was added.

Morsel.value¶

The value of the cookie.

Morsel.coded_value¶

The encoded value of the cookie — this is what should be sent.

Morsel.key¶

The name of the cookie.

Morsel.set(key, value, coded_value)[source]¶

Set the key, value and coded_value attributes.

Morsel.isReservedKey(K)[source]¶

Whether K is a member of the set of keys of a Morsel.

Morsel.output([attrs[, header]])[source]¶

Return a string representation of the Morsel, suitable to be sent as an HTTP header. By default, all the attributes are included, unless attrs is given, in which case it should be a list of attributes to use. header is by default "Set-Cookie:".

Morsel.js_output([attrs])[source]¶

Return an embeddable JavaScript snippet, which, if run on a browser which supports JavaScript, will act the same as if the HTTP header was sent.

The meaning for attrs is the same as in output().

Morsel.OutputString([attrs])[source]¶

Return a string representing the Morsel, without any surrounding HTTP or JavaScript.

The meaning for attrs is the same as in output().

9.3. Example¶

The following example demonstrates how to use the Cookie module.

Next Previous

© Copyright 2016.

Built with Sphinx using a theme provided by Read the Docs.