Lines Matching refs:rfc

20 :rfc:`2965` are handled.  RFC 2965 handling is switched off by default.
21 :rfc:`2109` cookies are parsed as Netscape cookies and subsequently treated
99    Netscape and :rfc:`2965` cookies.  By default, :rfc:`2109` cookies (ie. cookies
111    This class represents Netscape, :rfc:`2109` and :rfc:`2965` cookies.  It is not
127    https://curl.se/rfc/cookie_spec.html
133    :rfc:`2109` - HTTP State Management Mechanism
134       Obsoleted by :rfc:`2965`. Uses :mailheader:`Set-Cookie` with version=1.
136    :rfc:`2965` - HTTP State Management Mechanism
141       Unfinished errata to :rfc:`2965`.
143    :rfc:`2964` - Use of HTTP State Management
330       This loses information about :rfc:`2965` cookies, and also about newer or
423    Implement :rfc:`2965` protocol.
429    indicates to the server that we understand :rfc:`2965` cookies).
444 Both :rfc:`2965` and Netscape cookies are covered.  RFC 2965 handling is switched
524    If true, request that the :class:`CookieJar` instance downgrade :rfc:`2109` cookies
528    case RFC 2109 cookies are downgraded if and only if :rfc:`2965` handling is turned
541 :rfc:`2965` protocol strictness switches:
545    Follow :rfc:`2965` rules on unverifiable transactions (usually, an unverifiable
555    Apply :rfc:`2965` rules on unverifiable transactions even to Netscape cookies.
595    When setting cookies, require a full :rfc:`2965` domain-match.
619 cookie-attributes contain equivalent information, and because :rfc:`2109` cookies
630    Integer or :const:`None`.  Netscape cookies have :attr:`version` 0. :rfc:`2965` and
631    :rfc:`2109` cookies have a ``version`` cookie-attribute of 1.  However, note that
692    ``True`` if this cookie was received as an :rfc:`2109` cookie (ie. the cookie
764 :rfc:`2965` cookies, be more strict about domains when setting and returning