Searched refs:rfc (Results 1 – 25 of 236) sorted by relevance
12345678910
| /external/python/cpython3/Doc/library/ |
| D | http.rst | 62 ``100`` ``CONTINUE`` HTTP/1.1 :rfc:`7231`, Section 6.2.1
63 ``101`` ``SWITCHING_PROTOCOLS`` HTTP/1.1 :rfc:`7231`, Section 6.2.2
64 ``102`` ``PROCESSING`` WebDAV :rfc:`2518`, Section 10.1
65 ``103`` ``EARLY_HINTS`` An HTTP Status Code for Indicating Hints :rfc:`8297`
66 ``200`` ``OK`` HTTP/1.1 :rfc:`7231`, Section 6.3.1
67 ``201`` ``CREATED`` HTTP/1.1 :rfc:`7231`, Section 6.3.2
68 ``202`` ``ACCEPTED`` HTTP/1.1 :rfc:`7231`, Section 6.3.3
69 ``203`` ``NON_AUTHORITATIVE_INFORMATION`` HTTP/1.1 :rfc:`7231`, Section 6.3.4
70 ``204`` ``NO_CONTENT`` HTTP/1.1 :rfc:`7231`, Section 6.3.5
71 ``205`` ``RESET_CONTENT`` HTTP/1.1 :rfc:`7231`, Section 6.3.6
[all …]
|
| D | email.header.rst | 19 :rfc:`2822` is the base standard that describes the format of email messages.
20 It derives from the older :rfc:`822` standard which came into widespread use at
21 a time when most email was composed of ASCII characters only. :rfc:`2822` is a
29 :rfc:`2822`\ -compliant format. These RFCs include :rfc:`2045`, :rfc:`2046`,
30 :rfc:`2047`, and :rfc:`2231`. The :mod:`email` package supports these standards
54 field was properly :rfc:`2047` encoded. MIME-aware mail readers would show this
84 Optional *continuation_ws* must be :rfc:`2822`\ -compliant folding
110 In either case, when producing an :rfc:`2822`\ -compliant header using
111 :rfc:`2047` rules, the string will be encoded using the output codec of
|
| D | email.utils.rst | 32 Returns a string suitable for an :rfc:`2822`\ -compliant
78 Optional *charset* is the character set that will be used in the :rfc:`2047`
105 Attempts to parse a date according to the rules in :rfc:`2822`. however, some
107 guess correctly in such cases. *date* is a string containing an :rfc:`2822`
147 Returns a date string as per :rfc:`2822`, e.g.::
182 Decode the string *s* according to :rfc:`2231`.
187 Encode the string *s* according to :rfc:`2231`. Optional *charset* and
195 When a header parameter is encoded in :rfc:`2231` format,
202 :rfc:`2231` header is not known by Python; it defaults to ``'us-ascii'``.
210 Decode parameters list according to :rfc:`2231`. *params* is a sequence of
[all …]
|
| D | http.cookiejar.rst | 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
97 Netscape and :rfc:`2965` cookies. By default, :rfc:`2109` cookies (ie. cookies
109 This class represents Netscape, :rfc:`2109` and :rfc:`2965` cookies. It is not
125 https://curl.haxx.se/rfc/cookie_spec.html
131 :rfc:`2109` - HTTP State Management Mechanism
132 Obsoleted by :rfc:`2965`. Uses :mailheader:`Set-Cookie` with version=1.
134 :rfc:`2965` - HTTP State Management Mechanism
139 Unfinished errata to :rfc:`2965`.
141 :rfc:`2964` - Use of HTTP State Management
[all …]
|
| D | quopri.rst | 16 defined in :rfc:`1521`: "MIME (Multipurpose Internet Mail Extensions) Part One:
29 described in :rfc:`1522`: "MIME (Multipurpose Internet Mail Extensions)
42 as per :rfc:`1521`. *header* is a flag which controls if spaces are encoded
43 as underscores as per :rfc:`1522`.
|
| D | email.rst | 17 (:rfc:`2821`), NNTP, or other servers; those are functions of modules such as
19 RFC-compliant as possible, supporting :rfc:`5233` and :rfc:`6532`, as well as
20 such MIME-related RFCs as :rfc:`2045`, :rfc:`2046`, :rfc:`2047`, :rfc:`2183`,
21 and :rfc:`2231`.
|
| D | base64.rst | 19 :rfc:`3548`, which defines the Base16, Base32, and Base64 algorithms,
22 The :rfc:`3548` encodings are suitable for encoding binary data so that it can
31 defined in :rfc:`3548` (normal, and URL- and filesystem-safe) are supported.
36 newlines every 76 characters as per :rfc:`2045`. Note that if you are looking
37 for :rfc:`2045` support you probably want to be looking at the :mod:`email`
127 :rfc:`3548` allows for optional mapping of the digit 0 (zero) to the letter O
246 always ends with a newline, as per :rfc:`2045` (MIME).
254 there is a trailing newline, as per :rfc:`2045` (MIME).
275 …:rfc:`1521` - MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and…
|
| D | http.cookies.rst | 20 :rfc:`2109` and :rfc:`2068` specifications. It has since been discovered that
42 Exception failing because of :rfc:`2109` invalidity: incorrect attributes,
68 :rfc:`2109` - HTTP State Management Mechanism
129 Abstract a key/value pair, which has some :rfc:`2109` attributes.
132 :rfc:`2109` attributes, which are
220 valid :rfc:`2109` attribute.
236 Raise an error if key is not a valid :rfc:`2109` attribute, otherwise
|
| D | email.headerregistry.rst | 85 non-ASCII data will be :rfc:`2047` encoded.
121 An "unstructured" header is the default type of header in :rfc:`5322`.
126 In :rfc:`5322`, an unstructured header is a run of arbitrary text in the
127 ASCII character set. :rfc:`2047`, however, has an :rfc:`5322` compatible
131 into unicode, following the :rfc:`2047` rules for unstructured text. The
141 :rfc:`5322` specifies a very specific format for dates within email headers.
161 ``datetime`` according to the :rfc:`5322` rules; that is, it is set to::
244 per :rfc:`2045`, then the header object will have non-``None`` values for
304 ``quoted-printable``. See :rfc:`2045` for more information.
387 :rfc:`5322`.
[all …]
|
| /external/openssh/regress/ |
| D | keygen-convert.sh | 21 ${SSHKEYGEN} -q -e -f $OBJ/$t-key >$OBJ/$t-key-rfc || \
25 ${SSHKEYGEN} -q -e -f $OBJ/$t-key.pub >$OBJ/$t-key-rfc.pub || \
28 cmp $OBJ/$t-key-rfc $OBJ/$t-key-rfc.pub || \
32 ${SSHKEYGEN} -q -i -f $OBJ/$t-key-rfc >$OBJ/$t-rfc-imported || \
36 cmp $OBJ/$t-key-nocomment.pub $OBJ/$t-rfc-imported || \
39 rm -f $OBJ/$t-key $OBJ/$t-key.pub $OBJ/$t-key-rfc $OBJ/$t-key-rfc.pub \
40 $OBJ/$t-rfc-imported $OBJ/$t-key-nocomment.pub
|
| /external/cldr/docs/rfc/ |
| D | draft-davis-t-langtag-ext.css | 18 rfc:before {
24 rfc>front title {
31 rfc>front author:before {
38 rfc>front organization {
42 rfc>front address {
47 rfc>front email { display: block; }
48 rfc>front uri { display: block; }
50 rfc>front date:before {
57 rfc>front area:before { content: "Area: "; }
58 rfc>front area:after { content: "; "; }
[all …]
|
| D | rfc2629.xslt | 32 Support ?rfc editing processing instruction.
44 Experimental support for rfc-issue PI.
48 Support rfc private PI. Removed bogus code reporting the WG in the header.
279 non-standard whitespace handling). Fix default handling for /rfc/@category.
327 <!-- rfc compact PI -->
331 translate(/processing-instruction('rfc')[contains(.,'compact=')], '" ', ''),
335 <!-- rfc footer PI -->
339 translate(/processing-instruction('rfc')[contains(.,'footer=')], '" ', ''),
343 <!-- rfc header PI -->
347 translate(/processing-instruction('rfc')[contains(.,'header=')], '" ', ''),
[all …]
|
| /external/cldr/docs/ |
| D | README.md | 11 - draft-davis-t-langtag-ext: [html](rfc/draft-davis-t-langtag-ext.html) [txt](rfc/draft-davis-t-lan…
13 - draft-davis-u-langtag-ext-00: [html](rfc/draft-davis-u-langtag-ext-00.html) [txt](rfc/draft-davis…
|
| /external/python/cpython2/Doc/library/ |
| D | email.header.rst | 8 :rfc:`2822` is the base standard that describes the format of email messages.
9 It derives from the older :rfc:`822` standard which came into widespread use at
10 a time when most email was composed of ASCII characters only. :rfc:`2822` is a
18 :rfc:`2822`\ -compliant format. These RFCs include :rfc:`2045`, :rfc:`2046`,
19 :rfc:`2047`, and :rfc:`2231`. The :mod:`email` package supports these standards
43 field was properly :rfc:`2047` encoded. MIME-aware mail readers would show this
75 Optional *continuation_ws* must be :rfc:`2822`\ -compliant folding whitespace,
100 producing an :rfc:`2822`\ -compliant header using :rfc:`2047` rules, the
114 split long ASCII lines on, in rough support of :rfc:`2822`'s *highest
115 level syntactic breaks*. This doesn't affect :rfc:`2047` encoded lines.
|
| D | email.util.rst | 58 Attempts to parse a date according to the rules in :rfc:`2822`. however, some
60 guess correctly in such cases. *date* is a string containing an :rfc:`2822`
86 Returns a date string as per :rfc:`2822`, e.g.::
109 Returns a string suitable for an :rfc:`2822`\ -compliant
116 Decode the string *s* according to :rfc:`2231`.
121 Encode the string *s* according to :rfc:`2231`. Optional *charset* and
129 When a header parameter is encoded in :rfc:`2231` format,
136 :rfc:`2231` header is not known by Python; it defaults to ``us-ascii``.
144 Decode parameters list according to :rfc:`2231`. *params* is a sequence of
164 the POSIX standard while this module follows :rfc:`2822`.
|
| D | rfc822.rst | 16 message" as defined by the Internet standard :rfc:`2822`. [#]_ Such messages
18 also defines a helper class :class:`AddressList` for parsing :rfc:`2822`
20 :rfc:`2822` messages.
62 parameter, a comma-separated list of :rfc:`2822` addresses to be parsed. (The
97 Attempts to parse a date according to the rules in :rfc:`2822`. however, some
99 guess correctly in such cases. *date* is a string containing an :rfc:`2822`
114 while this module follows :rfc:`2822`.) If the input string has no timezone,
157 to index it) if the line is a legal :rfc:`2822` header; otherwise returns
351 .. [#] This module originally conformed to :rfc:`822`, hence the name. Since then,
352 :rfc:`2822` has been released as an update to :rfc:`822`. This module should be
[all …]
|
| D | quopri.rst | 17 defined in :rfc:`1521`: "MIME (Multipurpose Internet Mail Extensions) Part One:
31 "Q"-encoded headers as described in :rfc:`1522`: "MIME (Multipurpose Internet
43 and tabs appearing at the end of lines are always encoded, as per :rfc:`1521`.
|
| D | email.errors.rst | 26 Raised under some error conditions when parsing the :rfc:`2822` headers of a
32 first :rfc:`2822` header of the message, finding a continuation line before the
33 first :rfc:`2822` header is found, or finding a line in the headers which is
39 Raised under some error conditions when parsing the :rfc:`2822` headers of a
|
| /external/python/cryptography/docs/x509/ |
| D | index.rst | 5 defined in :rfc:`5280` (which obsoletes :rfc:`2459` and :rfc:`3280`). X.509
|
| /external/brotli/scripts/dictionary/ |
| D | step-01-download-rfc.py | 13 with open(path, "w") as rfc:
14 rfc.write(text)
|
| D | step-02-rfc-to-bin.py | 10 with open(rfc_path, "r") as rfc:
11 lines = rfc.readlines()
|
| /external/python/cryptography/docs/hazmat/primitives/ |
| D | keywrap.rst | 19 :rfc:`3394`.
37 :rfc:`3394`.
58 :rfc:`5649`.
76 :rfc:`5649`.
|
| /external/zopfli/ |
| D | README | 15 http://www.ietf.org/rfc/rfc1951.txt
17 http://www.ietf.org/rfc/rfc1950.txt
19 http://www.ietf.org/rfc/rfc1952.txt
|
| /external/python/cryptography/docs/development/ |
| D | test-vectors.rst | 51 * X25519 and X448 test vectors from :rfc:`7748`.
53 * Ed448 test vectors from :rfc:`8032`.
127 several standardized Diffie-Hellman groups from :rfc:`3526`.
130 Diffie-Hellman examples from appendix A.1, A.2 and A.3 of :rfc:`5114`.
157 :rfc:`5114` 2048 bit DH parameters with 224 bit subgroup.
166 Brainpool vectors from :rfc:`7027`.
208 in violation of :rfc:`5280`.
234 attribute type from :rfc:`5280`.
275 ``uniformResourceIdentifier`` general names with IDNA (:rfc:`5895`) encoding.
278 name with a wildcard IDNA (:rfc:`5895`) domain.
[all …]
|
| /external/python/cryptography/docs/development/custom-vectors/ |
| D | arc4.rst | 5 vectors for key lengths not available in :rfc:`6229`. All the vectors
12 in :rfc:`6229`. Then the following Python script was run to generate the
|
12345678910