Hypertext Transfer Protocol (HTTP) Parameters Last Updated 2013-01-15 This registry is also available in plain text. Registries included below * HTTP Content-Coding Values * HTTP Transfer-Coding Values * HTTP Forwarded Parameters * HTTP Preferences HTTP Content-Coding Values Registration Procedures First Come First Served with specification recommended Experts Primary: Roy Fielding; Secondary: Mark Nottingham Reference [RFC2616] Name Description Reference Notes compress UNIX "compress" program method [RFC2616] Section 3.5 deflate "zlib" format [RFC1950] with "deflate" [RFC2616] Section 3.5 compression exi W3C Efficient XML Interchange [J. Schneider and T. Kamiya, Eds. "Efficient XML Interchange (EXI) Format 1.0", W3C Working Draft, 19 Sep 2008] gzip Same as GNU zip [RFC1952] [RFC2616] Section 3.5 identity No transformation [RFC2616] Section 3.5 pack200-gzip Network Transfer Format for Java [JSR 200: Network Transfer Format for Java][Kumar_Srinivasan][John_Rose] Archives HTTP Transfer-Coding Values Registration Procedures First Come First Served with specification recommended Experts Primary: Roy Fielding; Secondary: Mark Nottingham Reference [RFC2616] Name Description Reference Notes chunked Transfer in a series of chunks [RFC2616] Section 3.6.1 compress UNIX "compress" program method [RFC2616] Section 3.6 deflate "zlib" format [RFC1950] with "deflate" compression [RFC2616] Section 3.6 gzip Same as GNU zip [RFC1952] [RFC2616] Section 3.6 identity (withdrawn in errata to [RFC2616]) [RFC2616] Section 3.6 HTTP Forwarded Parameters Registration Procedures IETF Review Reference [RFC-ietf-appsawg-http-forwarded-10] Name Description Reference Notes by IP-address of incoming interface of a proxy [RFC-ietf-appsawg-http-forwarded-10] Section 5.1 for IP-address of client making a request through a proxy [RFC-ietf-appsawg-http-forwarded-10] Section 5.2 host Host header field of the incoming request [RFC-ietf-appsawg-http-forwarded-10] Section 5.3 proto Application protocol used for incoming request [RFC-ietf-appsawg-http-forwarded-10] Section 5.4 HTTP Preferences Registration Procedures Specification Required Reference [RFC-snell-http-prefer-18] Preference Value Description Reference respond-async Indicates that the client prefers the server to respond [RFC-snell-http-prefer-18], Section 4.1 asynchronously to a request. When value is "minimal", indicates that the client prefers the One of either "minimal" or server return a minimal response to a request. When value is return "representation" "representation", indicates that the client prefers the server [RFC-snell-http-prefer-18], Section 4.2 to include a representation of the current state of the resource in response to a request. Indicates an upper bound to the length of time the client wait expects it will take the server to process the request once it [RFC-snell-http-prefer-18], Section 4.3 has been received. When value is "strict", indicates that the client wishes the One of either "strict" or server to apply strict validation and error handling to the handling "lenient" processing of a request. When value is "lenient", indicates [RFC-snell-http-prefer-18], Section 4.4 that the client wishes the server to apply lenient validation and error handling to the processing of the request. 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