Hypertext Transfer Protocol (HTTP) Parameters

Last Updated
2017-04-18
Available Formats

XML

HTML

Plain text

Registries included below

HTTP Content Coding Registry

Registration Procedure(s)
IETF Review
Reference
[RFC7231]
Available Formats

CSV
Name Description Reference Notes
aes128gcm AES-GCM encryption with a 128-bit content encryption key [RFC-ietf-httpbis-encryption-encoding-09]
br Brotli Compressed Data Format [RFC7932]
compress UNIX "compress" data format [Welch, T., "A Technique for High Performance Data Compression", IEEE Computer 17(6), June 1984.] [RFC7230] Section 4.2.1
deflate "deflate" compressed data ([RFC1951]) inside the "zlib" data format ([RFC1950]) [RFC7230] Section 4.2.2
exi W3C Efficient XML Interchange [W3C Recommendation: Efficient XML Interchange (EXI) Format]
gzip GZIP file format [RFC1952] [RFC7230] Section 4.2.3
identity Reserved (synonym for "no encoding" in Accept-Encoding) [RFC7231] Section 5.3.4
pack200-gzip Network Transfer Format for Java Archives [JSR 200: Network Transfer Format for Java][Kumar_Srinivasan][John_Rose]
x-compress Deprecated (alias for compress) [RFC7230] Section 4.2.1
x-gzip Deprecated (alias for gzip) [RFC7230] Section 4.2.3

HTTP Transfer Coding Registry

Registration Procedure(s)
IETF Review
Reference
[RFC7230]
Available Formats

CSV
Name Description Reference Notes
chunked Transfer in a series of chunks [RFC7230] Section 4.1
compress UNIX "compress" data format [Welch, T., "A Technique for High Performance Data Compression", IEEE Computer 17(6), June 1984.] [RFC7230] Section 4.2.1
deflate "deflate" compressed data ([RFC1951]) inside the "zlib" data format ([RFC1950]) [RFC7230] Section 4.2.2
gzip GZIP file format [RFC1952] [RFC7230] Section 4.2.3
identity (withdrawn in errata to [RFC2616]) [RFC2616] Section 3.6
x-compress Deprecated (alias for compress) [RFC7230] Section 4.2.1
x-gzip Deprecated (alias for gzip) [RFC7230] Section 4.2.3

HTTP Forwarded Parameters

Registration Procedure(s)
IETF Review
Reference
[RFC7239]
Available Formats

CSV
Name Description Reference Notes
by IP-address of incoming interface of a proxy [RFC7239] Section 5.1
for IP-address of client making a request through a proxy [RFC7239] Section 5.2
host Host header field of the incoming request [RFC7239] Section 5.3
proto Application protocol used for incoming request [RFC7239] Section 5.4

HTTP Preferences

Registration Procedure(s)
Specification Required
Expert(s)
James M Snell, Julian Reschke
Reference
[RFC7240]
Available Formats

CSV
Preference Value Description Reference
respond-async Indicates that the client prefers that the server respond asynchronously to a request. [RFC7240], Section 4.1
return One of either "minimal" or "representation" When the value is "minimal", it indicates that the client prefers that the server return a minimal response to a request. When the value is "representation", it indicates that the client prefers that the server include a representation of the current state of the resource in response to a request. [RFC7240], Section 4.2
wait Indicates an upper bound to the length of time the client expects it will take the server to process the request once it has been received. [RFC7240], Section 4.3
handling One of either "strict" or "lenient" When value is "strict", it indicates that the client wishes the server to apply strict validation and error handling to the processing of a request. When the value is "lenient", it indicates that the client wishes the server to apply lenient validation and error handling to the processing of the request. [RFC7240], Section 4.4
depth-noroot The "depth-noroot" preference indicates that the client wishes for the server to exclude the target (root) resource from processing by the HTTP method and only apply the HTTP method to the target resource's subordinate resources. This preference is only intended to be used with HTTP methods whose definitions explicitly provide support for the Depth [RFC4918] header field. Furthermore, this preference only applies when the Depth header field has a value of "1" or "infinity" (either implicitly or explicitly). [RFC8144], Section 4

HTTP Range Unit Registry

Registration Procedure(s)
IETF Review
Reference
[RFC7233]
Available Formats

CSV
Name Description Reference Notes
bytes a range of octets [RFC7233] Section 2.1
none reserved as keyword, indicating no ranges are supported [RFC7233] Section 2.3

People

ID Name Contact URI Last Updated
[Kumar_Srinivasan] Kumar Srinivasan mailto:Kumar.Srinivasan&Sun.COM 2006-10-27
[John_Rose] John Rose mailto:John.Rose&Sun.COM 2006-10-27