        ``"Wdy, DD-Mon-YY HH:MM:SS GMT"`` or a ``datetime.datetime`` object
        in UTC. If ``expires`` is a ``datetime`` object, the ``max_age``
        will be calculated.
      * Use ``domain`` if you want to set a cross-domain cookie. For example,
        ``domain=".lawrence.com"`` will set a cookie that is readable by
        the domains www.lawrence.com, blogs.lawrence.com and
        calendars.lawrence.com. Otherwise, a cookie will only be readable by
        the domain that set it.
      * Use ``httponly=True`` if you want to prevent client-side
        JavaScript from having access to the cookie.
  
        HTTPOnly_ is a flag included in a Set-Cookie HTTP response
        header. It is not part of the :rfc:`2109` standard for cookies,
 
</s> remove ``".example.com"`` to allow a POST request from a form on one subdomain to be
 </s> add ``"example.com"`` to allow a POST request from a form on one subdomain to be </s> remove ``".example.com"`` (note the leading dot!) for cross-domain cookies, or use
``None`` for a standard domain cookie.
 </s> add ``"example.com"`` for cross-domain cookies, or use ``None`` for a standard
domain cookie. </s> remove ``".example.com"`` (note the leading dot!) for cross-domain cookies, or use
``None`` for a standard domain cookie.
 </s> add ``"example.com"`` for cross-domain cookies, or use ``None`` for a standard
domain cookie. </s> remove # A string like ".example.com", or None for standard domain cookie.
 </s> add # A string like "example.com", or None for standard domain cookie.
      ``domain="example.com"`` will set a cookie that is readable by the
      domains www.example.com, blog.example.com, etc. Otherwise, a cookie will
      only be readable by the domain that set it.
        ``"Wdy, DD-Mon-YY HH:MM:SS GMT"`` or a ``datetime.datetime`` object
        in UTC. If ``expires`` is a ``datetime`` object, the ``max_age``
        will be calculated.
      * Use ``domain`` if you want to set a cross-domain cookie. For example,
      ``domain="example.com"`` will set a cookie that is readable by the
      domains www.example.com, blog.example.com, etc. Otherwise, a cookie will
      only be readable by the domain that set it.
      ``domain="example.com"`` will set a cookie that is readable by the
      domains www.example.com, blog.example.com, etc. Otherwise, a cookie will
      only be readable by the domain that set it.
      ``domain="example.com"`` will set a cookie that is readable by the
      domains www.example.com, blog.example.com, etc. Otherwise, a cookie will
      only be readable by the domain that set it.
      ``domain="example.com"`` will set a cookie that is readable by the
      domains www.example.com, blog.example.com, etc. Otherwise, a cookie will
      only be readable by the domain that set it.
      * Use ``httponly=True`` if you want to prevent client-side
        JavaScript from having access to the cookie.
  
        HTTPOnly_ is a flag included in a Set-Cookie HTTP response
        header. It is not part of the :rfc:`2109` standard for cookies,
keep keep keep keep replace replace replace replace keep keep keep keep keep
 Fixed #28741 -- Removed unnecessary leading dot from cross-domain cookie examples. 
docs/ref/request-response.txt