Dancer2...::Cookie(3)

okay so this is Dancer2::Core::Cookie, a page from the User Contributed Perl Documentation section of the manual (section 3, iykyk). it's the cookie-representing class and honestly? she's serving exactly one job and doing it flawlessly. ✨


🌸 VERSION 🌸

this is version 2.2.1. iconic, no notes.


✨ SYNOPSIS ✨

here's the vibe, bestie:

use Dancer2::Core::Cookie;

my $cookie = Dancer2::Core::Cookie->new(
    name => $cookie_name, value => $cookie_value
);

my $value = $cookie->value;

print "$cookie"; # objects stringify to their value.

see that last line? the object just becomes its value when you stringify it. main character energy fr fr. πŸ’…


πŸ“ DESCRIPTION πŸ“

Dancer2::Core::Cookie provides a HTTP cookie object to work with cookies. that's it, that's the whole thing, and she eats every single time. 🫢


πŸŽ€ ATTRIBUTES πŸŽ€

πŸ’œ value

The cookie's value.

(Note that cookie objects use overloading to stringify to their value, so if you say e.g. return "Hi, $cookie", you'll get the cookie's value there. literally the object is just vibing as its own value, we love a shapeshifter.)

In list context, returns a list of potentially multiple values; in scalar context, returns just the first value. (So, if you expect a cookie to have multiple values, use list context. do not come crying to me when you get the first one only, bestie, the manpage warned you. 😭)

πŸ’œ name

The cookie's name. simple. elegant. her government name.

πŸ’œ expires

The cookie's expiration date. There are several formats.

  • Unix epoch time like 1288817656 to mean "Wed, 03-Nov-2010 20:54:16 GMT"
  • It also supports a human readable offset from the current time such as "2 hours". See the documentation of Dancer2::Core::Time for details of all supported formats.

πŸ’œ domain

The cookie's domain.

πŸ’œ path

The cookie's path.

πŸ’œ secure

If true, it instructs the client to only serve the cookie over secure connections such as https. lock her down, protect the girlies. πŸ”₯

πŸ’œ http_only

By default, cookies are created with a property, named "HttpOnly", that can be used for security, forcing the cookie to be used only by the server (via HTTP) and not by any JavaScript code.

If your cookie is meant to be used by some JavaScript code, set this attribute to 0.

fr fr, this default is protecting you. if you flip it to 0, you're opening the door to JS on purpose, so make sure that's actually what you want. πŸ™ˆ

πŸ’œ same_site

Whether the cookie ought not to be sent along with cross-site requests. Valid values are "Strict", "Lax", or "None". Default is unset. Refer to RFC6265bis <https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site> for further details regarding same-site context.


🌈 METHODS 🌈

Create a new Dancer2::Core::Cookie object.

You can set any attribute described in the ATTRIBUTES section above. go wild, pick your faves. πŸ’…

Creates a proper HTTP cookie header from the content. she's ready for the wire, periodt. πŸ‘‘

πŸ¦‹ values

Returns all values associated with this cookie, always a list. (So in scalar context, you will get the count. sneaky little detail, but that's how it goes.)


🌟 AUTHOR 🌟

Dancer Core Developers β€” the collective, the icon, the blueprint. πŸ‘‘


This software is copyright (c) 2026 by Alexis Sukrieh.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.


and that's the whole page bestie!! 🧚 this was generated with perl v5.42.3 on 2026-09-20, so if you're reading this from the future, hiii, hope the cookies are still chewy. πŸͺ bye mwah πŸ’‹

πŸ“¦ where this page comes from