Searched refs:RFC (Results 1 – 25 of 186) sorted by relevance
12345678
10 RFC 959 - The FTP protocol12 RFC 1635 - How to Use Anonymous FTP14 RFC 1738 - Uniform Resource Locators16 RFC 1777 - defines the LDAP protocol18 RFC 1808 - Relative Uniform Resource Locators20 RFC 1867 - Form-based File Upload in HTML22 RFC 1950 - ZLIB Compressed Data Format Specification24 RFC 1951 - DEFLATE Compressed Data Format Specification26 RFC 1952 - gzip compression format28 RFC 1959 - LDAP URL syntax[all …]
229 | :const:`CONTINUE` | ``100`` | HTTP/1.1, `RFC 2616, Section …233 | :const:`SWITCHING_PROTOCOLS` | ``101`` | HTTP/1.1, `RFC 2616, Section …237 | :const:`PROCESSING` | ``102`` | WEBDAV, `RFC 2518, Section 10.1 …240 | :const:`OK` | ``200`` | HTTP/1.1, `RFC 2616, Section …244 | :const:`CREATED` | ``201`` | HTTP/1.1, `RFC 2616, Section …248 | :const:`ACCEPTED` | ``202`` | HTTP/1.1, `RFC 2616, Section …252 | :const:`NON_AUTHORITATIVE_INFORMATION` | ``203`` | HTTP/1.1, `RFC 2616, Section …256 | :const:`NO_CONTENT` | ``204`` | HTTP/1.1, `RFC 2616, Section …260 | :const:`RESET_CONTENT` | ``205`` | HTTP/1.1, `RFC 2616, Section …264 | :const:`PARTIAL_CONTENT` | ``206`` | HTTP/1.1, `RFC 2616, Section …[all …]
26 :rfc:`2965` are handled. RFC 2965 handling is switched off by default.28 either as Netscape or RFC 2965 cookies according to the 'policy' in effect.33 introduced with RFC 2965.98 Netscape and RFC 2965 cookies. By default, RFC 2109 cookies (ie. cookies100 1) are treated according to the RFC 2965 rules. However, if RFC 2965 handling101 is turned off or :attr:`rfc2109_as_netscape` is ``True``, RFC 2109 cookies are110 This class represents Netscape, RFC 2109 and RFC 2965 cookies. It is not132 Obsoleted by RFC 2965. Uses :mailheader:`Set-Cookie` with version=1.139 Unfinished errata to RFC 2965.326 This loses information about RFC 2965 cookies, and also about newer or[all …]
6 :synopsis: String preparation, as per RFC 345322 preparation procedure, after which they have a certain normalized form. The RFC28 The module :mod:`stringprep` only exposes the tables from RFC 3454. As these34 There are two kinds of tables in the RFC: sets and mappings. For a set,
499 This section details this module's level of compliance with the RFC.503 This module does not comply with the RFC in a strict fashion, implementing some510 Since the RFC permits RFC-compliant parsers to accept input texts that are not511 RFC-compliant, this module's deserializer is technically RFC-compliant under517 The RFC requires that JSON be represented using either UTF-8, UTF-16, or526 As permitted, though not required, by the RFC, this module's serializer sets530 The RFC prohibits adding a byte order mark (BOM) to the start of a JSON text,532 The RFC permits, but does not require, JSON deserializers to ignore an initial536 The RFC does not explicitly forbid JSON strings which contain byte sequences546 The RFC does not permit the representation of infinite or NaN number values.[all …]
2 :mod:`uuid` --- UUID objects according to RFC 41226 :synopsis: UUID objects (universally unique identifiers) according to RFC 412245 variant and version number set according to RFC 4122, overriding bits in the101 The UUID as a URN as specified in RFC 4122.124 with its eighth bit set to 1 as recommended in RFC 4122. "Hardware address"
28 these types. This document obsoletes RFC 3534.33 2. Changes Since RFC 3534 . . . . . . . . . . . . . . . . . . 260 RFC 5334 Ogg Media Types September 200894 2. Changes Since RFC 3534116 RFC 5334 Ogg Media Types September 2008172 RFC 5334 Ogg Media Types September 2008228 RFC 5334 Ogg Media Types September 2008284 RFC 5334 Ogg Media Types September 2008340 RFC 5334 Ogg Media Types September 2008375 Optional parameters: codecs, whose syntax is defined in RFC 4281.[all …]
35 document are to be interpreted as described in BCP 14, RFC 2119 [2].60 RFC 3533 OGG May 2003116 RFC 3533 OGG May 2003172 RFC 3533 OGG May 2003228 RFC 3533 OGG May 2003284 RFC 3533 OGG May 2003340 RFC 3533 OGG May 2003396 RFC 3533 OGG May 2003452 RFC 3533 OGG May 2003508 RFC 3533 OGG May 2003[all …]
12 @emph{RFC 2616}: Fielding, R., Gettys, J., Mogul, J., Frystyk, H., and T. Berners-Lee,13 "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2016, January 1997.16 @emph{RFC 2617}: Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P.,17 Luotonen, A., and L. Stewart, "HTTP Authentication: Basic and Digest Access Authentication", RFC 26…
60 RFC 5071 PXELINUX Options December 200771 3.4. Response to RFC 3942 . . . . . . . . . . . . . . . . . . . 576 4.4. Response to RFC 3942 . . . . . . . . . . . . . . . . . . . 682 5.4. Response to RFC 3942 . . . . . . . . . . . . . . . . . . . 888 6.4. Response to RFC 3942 . . . . . . . . . . . . . . . . . . . 10116 RFC 5071 PXELINUX Options December 2007172 RFC 5071 PXELINUX Options December 2007180 assignments are done within RFC 3942's provisions for documenting201 in this document are to be interpreted as described in RFC 2119 [2].228 RFC 5071 PXELINUX Options December 2007[all …]
26 class RFC(LisaTest): class34 super(RFC, cls).runExperiments(args, kwargs)
11 RFC 2384, RFC 5092 and IETF draft draft-earhart-url-smtp-00.txt
7 Tells curl to respect RFC 7230/6.4.2 and not convert POST requests into GET8 requests when following a 302 redirection. The non-RFC behaviour is ubiquitous
7 Tells curl to respect RFC 7230/6.4.2 and not convert POST requests into GET8 requests when following a 303 redirection. The non-RFC behaviour is ubiquitous
7 Tells curl to respect RFC 7230/6.4.2 and not convert POST requests into GET8 requests when following a 301 redirection. The non-RFC behaviour is ubiquitous
13 considered insecure (see RFC 7568).
13 considered insecure (see RFC 6176).
60 RFC 1950 ZLIB Compressed Data Format Specification May 1996116 RFC 1950 ZLIB Compressed Data Format Specification May 1996155 specification was converted to RFC style.172 RFC 1950 ZLIB Compressed Data Format Specification May 1996228 RFC 1950 ZLIB Compressed Data Format Specification May 1996284 RFC 1950 ZLIB Compressed Data Format Specification May 1996340 RFC 1950 ZLIB Compressed Data Format Specification May 1996396 RFC 1950 ZLIB Compressed Data Format Specification May 1996416 Randers-Pehrson converted this document to RFC and HTML format.452 RFC 1950 ZLIB Compressed Data Format Specification May 1996[all …]
60 RFC 1951 DEFLATE Compressed Data Format Specification May 1996116 RFC 1951 DEFLATE Compressed Data Format Specification May 1996172 RFC 1951 DEFLATE Compressed Data Format Specification May 1996185 specification to RFC style.228 RFC 1951 DEFLATE Compressed Data Format Specification May 1996284 RFC 1951 DEFLATE Compressed Data Format Specification May 1996340 RFC 1951 DEFLATE Compressed Data Format Specification May 1996396 RFC 1951 DEFLATE Compressed Data Format Specification May 1996452 RFC 1951 DEFLATE Compressed Data Format Specification May 1996508 RFC 1951 DEFLATE Compressed Data Format Specification May 1996[all …]
60 RFC 1952 GZIP File Format Specification May 1996116 RFC 1952 GZIP File Format Specification May 1996166 specification to RFC style.172 RFC 1952 GZIP File Format Specification May 1996228 RFC 1952 GZIP File Format Specification May 1996284 RFC 1952 GZIP File Format Specification May 1996340 RFC 1952 GZIP File Format Specification May 1996396 RFC 1952 GZIP File Format Specification May 1996452 RFC 1952 GZIP File Format Specification May 1996508 RFC 1952 GZIP File Format Specification May 1996[all …]
41 * RFC 3533 documentation of the format by Silvia Pfeiffer at CSIRO42 * RFC 3534 documentation of the application/ogg mime-type by Linus Walleij
1 # RFC 7539, section 2.5.2.8 # RFC 7539, section A.3.
13 with the standard, it is the code in this RFC that shall remain normative.14 To build from the git repository instead of using this RFC, follow these
4 counter to RFC 2822, there's no separating newline here
10 RFC 2046, $5.1.5, but is not illegal