<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="http-parameters.xsl"?>
<?oxygen RNGSchema="http-parameters.rng" type="xml"?>
<registry xmlns="http://www.iana.org/assignments" id="http-parameters">
  <title>Hypertext Transfer Protocol (HTTP) Parameters</title>
  <updated>2013-01-15</updated>



  <registry id="http-parameters-1">
    <title>HTTP Content-Coding Values</title>
    <xref type="rfc" data="rfc2616"/>
    <registration_rule>First Come First Served with specification recommended</registration_rule>
    <expert>Primary: Roy Fielding; Secondary: Mark Nottingham</expert>
    
    <record>
      <name>compress</name>
      <description>UNIX "compress" program method</description>
      <xref type="rfc" data="rfc2616"/>
      <note>Section 3.5</note>
    </record>
    <record>
      <name>deflate</name>
      <description>"zlib" format <xref type="rfc" data="rfc1950"/> with "deflate" compression</description>
      <xref type="rfc" data="rfc2616"/>
      <note>Section 3.5</note>
    </record>
    <record>
      <name>exi</name>
      <description>W3C Efficient XML Interchange</description>
      <xref type="uri" data="http://www.w3.org/TR/exi/">J. Schneider and T. Kamiya, Eds. "Efficient XML Interchange (EXI) Format 1.0", W3C
Working Draft, 19 Sep 2008</xref>
    </record>
    <record>
      <name>gzip</name>
      <description>Same as GNU zip <xref type="rfc" data="rfc1952"/></description>
      <xref type="rfc" data="rfc2616"/>
      <note>Section 3.5</note>
    </record>
    <record>
      <name>identity</name>
      <description>No transformation</description>
      <xref type="rfc" data="rfc2616"/>
      <note>Section 3.5</note>
    </record>
    <record date="2006-10-27">
      <name>pack200-gzip</name>
      <description>Network Transfer Format for Java Archives</description>
      <xref type="uri" data="http://www.jcp.org/en/jsr/detail?id=200">JSR 200: Network Transfer Format for Java</xref>
      <xref type="person" data="Kumar_Srinivasan"/>
      <xref type="person" data="John_Rose"/>
    </record>
  </registry>
  
  
  
  <registry id="http-parameters-2">
    <title>HTTP Transfer-Coding Values</title>
    <xref type="rfc" data="rfc2616"/>
    <registration_rule>First Come First Served with specification recommended</registration_rule>
    <expert>Primary: Roy Fielding; Secondary: Mark Nottingham</expert>
    
    <record>
      <name>chunked</name>
      <description>Transfer in a series of chunks</description>
      <xref type="rfc" data="rfc2616"/>
      <note>Section 3.6.1</note>
    </record>
    <record>
      <name>compress</name>
      <description>UNIX "compress" program method</description>
      <xref type="rfc" data="rfc2616"/>
      <note>Section 3.6</note>
    </record>
    <record>
      <name>deflate</name>
      <description>"zlib" format <xref type="rfc" data="rfc1950"/> with "deflate" compression</description>
      <xref type="rfc" data="rfc2616"/>
      <note>Section 3.6</note>
    </record>
    <record>
      <name>gzip</name>
      <description>Same as GNU zip <xref type="rfc" data="rfc1952"/></description>
      <xref type="rfc" data="rfc2616"/>
      <note>Section 3.6</note>
    </record>
    <record>
      <name>identity</name>
      <description>(withdrawn in errata to <xref type="rfc" data="rfc2616"/>)</description>
      <xref type="rfc" data="rfc2616"/>
      <note>Section 3.6</note>
    </record>
  </registry>
  
  
  
  <registry id="forwarded">
    <title>HTTP Forwarded Parameters</title>
    <xref type="draft" data="RFC-ietf-appsawg-http-forwarded-10"/>
    <registration_rule>IETF Review</registration_rule>
    
    <record>
      <name>by</name>
      <description>IP-address of incoming interface of a proxy</description>
      <xref type="draft" data="RFC-ietf-appsawg-http-forwarded-10"/>
      <note>Section 5.1</note>
    </record>
    <record>
      <name>for</name>
      <description>IP-address of client making a request through a proxy</description>
      <xref type="draft" data="RFC-ietf-appsawg-http-forwarded-10"/>
      <note>Section 5.2</note>
    </record>
    <record>
      <name>host</name>
      <description>Host header field of the incoming request</description>
      <xref type="draft" data="RFC-ietf-appsawg-http-forwarded-10"/>
      <note>Section 5.3</note>
    </record>
    <record>
      <name>proto</name>
      <description>Application protocol used for incoming request</description>
      <xref type="draft" data="RFC-ietf-appsawg-http-forwarded-10"/>
      <note>Section 5.4</note>
    </record>
  </registry>
  
  
    <registry id="preferences">
    <title>HTTP Preferences</title>
    <xref type="draft" data="RFC-snell-http-prefer-18"/>
    <registration_rule>Specification Required</registration_rule>
    
    <record>
      <name>respond-async</name>
      <value/>
      <description>Indicates that the client prefers the server to respond asynchronously to a request.</description>
      <spec><xref type="draft" data="RFC-snell-http-prefer-18"/>, Section 4.1</spec>
    </record>    
    <record>
      <name>return</name>
      <value>One of either "minimal" or "representation"</value>
      <description>When value is "minimal", indicates that the client
      prefers the server return a minimal response to a request.  When
      value is "representation", indicates that the client prefers the
      server to include a representation of the current state of the 
      resource in response to a request.</description>
      <spec><xref type="draft" data="RFC-snell-http-prefer-18"/>, Section 4.2</spec>
    </record>    
     <record>
      <name>wait</name>
      <value/>
      <description>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.</description>
      <spec><xref type="draft" data="RFC-snell-http-prefer-18"/>, Section 4.3</spec>
    </record>     
    <record>
      <name>handling</name>
      <value>One of either "strict" or "lenient"</value>
      <description>When value is "strict", indicates that the client
      wishes the server to apply strict validation and error handling to
      the processing of a request.  When value is "lenient", indicates
      that the client wishes the server to apply lenient validation and
      error handling to the processing of the request.</description>
      <spec><xref type="draft" data="RFC-snell-http-prefer-18"/>, Section 4.4</spec>
    </record>
  
    </registry>
  
  
  <people>
    <person id="Kumar_Srinivasan">
      <name>Kumar Srinivasan</name>
      <uri>mailto:Kumar.Srinivasan&amp;Sun.COM</uri>
      <updated>2006-10-27</updated>
    </person>
    <person id="John_Rose">
      <name>John Rose</name>
      <uri>mailto:John.Rose&amp;Sun.COM</uri>
      <updated>2006-10-27</updated>
    </person>
  </people>
</registry>
