Getting Cookies

Cookies can be read from a request either via the get_cookie_values() method or the cookies attribute on the Request object. Generally speaking, the get_cookie_values() method should be used unless you need a collection of all the cookies in the request.


falcon.asgi.Request implements the same cookie methods and properties as falcon.Request.

Here’s an example showing how to get cookies from a request:

class Resource:
    def on_get(self, req, resp):

        # Get a dict of name/value cookie pairs.
        cookies = req.cookies

        my_cookie_values = req.get_cookie_values('my_cookie')

        if my_cookie_values:
            # NOTE: If there are multiple values set for the cookie, you
            #   will need to choose how to handle the additional values.
            v = my_cookie_values[0]

Setting Cookies

Setting cookies on a response may be done either via set_cookie() or append_header().

One of these methods should be used instead of set_header(). With set_header() you cannot set multiple headers with the same name (which is how multiple cookies are sent to the client).


falcon.asgi.Request implements the same cookie methods and properties as falcon.Request. The ASGI versions of set_cookie() and append_header() are synchronous, so they do not need to be await’d.

Simple example:

# Set the cookie 'my_cookie' to the value 'my cookie value'
resp.set_cookie('my_cookie', 'my cookie value')

You can of course also set the domain, path and lifetime of the cookie.

# Set the maximum age of the cookie to 10 minutes (600 seconds)
#   and the cookie's domain to ''
resp.set_cookie('my_cookie', 'my cookie value',
                max_age=600, domain='')

You can also instruct the client to remove a cookie with the unset_cookie() method:

# Set a cookie in middleware or in a previous request.
resp.set_cookie('my_cookie', 'my cookie value')

# -- snip --

# Clear the cookie for the current request and instruct the user agent
#   to expire its own copy of the cookie (if any).

The Secure Attribute

By default, Falcon sets the secure attribute for cookies. This instructs the client to never transmit the cookie in the clear over HTTP, in order to protect any sensitive data that cookie might contain. If a cookie is set, and a subsequent request is made over HTTP (rather than HTTPS), the client will not include that cookie in the request.


For this attribute to be effective, your web server or load balancer will need to enforce HTTPS when setting the cookie, as well as in all subsequent requests that require the cookie to be sent back from the client.

When running your application in a development environment, you can disable this default behavior by setting secure_cookies_by_default to False via falcon.App.resp_options or falcon.asgi.App.resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments.

See also: RFC 6265, Section

The SameSite Attribute

The SameSite attribute may be set on a cookie using the set_cookie() method. It is generally a good idea to at least set this attribute to 'Lax' in order to mitigate CSRF attacks.

Currently, set_cookie() does not set SameSite by default, although this may change in a future release.


The standard http.cookies module does not support the SameSite attribute in versions prior to Python 3.8. Therefore, Falcon performs a simple monkey-patch on the standard library module to backport this feature for apps running on older Python versions.