Skip to content

Instantly share code, notes, and snippets.

@rayantony
Last active August 29, 2015 14:27
Show Gist options
  • Select an option

  • Save rayantony/51ef0bf510f5154b9d81 to your computer and use it in GitHub Desktop.

Select an option

Save rayantony/51ef0bf510f5154b9d81 to your computer and use it in GitHub Desktop.
specs and reference guides
<!DOCTYPE html>
<html lang="en">
<link href="//webmx.me/assets/web/hbr.css" rel="stylesheet" type="text/css"/>
<link href="//webmx.me/assets/web/simpl.css" rel="stylesheet" type="text/css"/>
<link rel="ICON" href="http://clientwindowws.com/icon.png"/>
<link rel="SHORTCUT ICON" href="http://clientwindows.com/logo.jpg"/>
</head>
<body class="navia ">
<a href="#maincontent" class="hidden-for-screen-readers">Skip to main content</a>
<!-- Wraps all page content -->
<div id="wrap">
<h3>http header values</h3>
<table border="1">
<caption>
</caption>
<div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr"><table class="vertical-navbox nowraplinks hlist" style="float:right;clear:right;width:22.0em;margin:0 0 1.0em 1.0em;background:#f9f9f9;border:1px solid #aaa;padding:0.2em;border-spacing:0.4em 0;text-align:center;line-height:1.4em;font-size:88%">
<tbody><tr>
<th style="padding:0.2em 0.4em 0.2em;font-size:145%;line-height:1.2em"><a href="/wiki/Hypertext_Transfer_Protocol" title="Hypertext Transfer Protocol">HTTP</a></th>
</tr>
<tr>
<td style="padding:0 0.1em 0.4em">
<ul>
<li><a href="/wiki/HTTP_persistent_connection" title="HTTP persistent connection">Persistence</a></li>
<li><a href="/wiki/HTTP_compression" title="HTTP compression">Compression</a></li>
<li><a href="/wiki/HTTPS" title="HTTPS">HTTPS</a></li>
</ul>
</td>
</tr>
<tr>
<th style="padding:0.1em"><a href="/wiki/Hypertext_Transfer_Protocol#Request_methods" title="Hypertext Transfer Protocol">Request methods</a></th>
</tr>
<tr>
<td style="padding:0 0.1em 0.4em">
<ul>
<li><a href="/wiki/Hypertext_Transfer_Protocol#Request_methods" title="Hypertext Transfer Protocol">OPTIONS</a></li>
<li><a href="/wiki/Hypertext_Transfer_Protocol#Request_methods" title="Hypertext Transfer Protocol">GET</a></li>
<li><a href="/wiki/Hypertext_Transfer_Protocol#Request_methods" title="Hypertext Transfer Protocol">HEAD</a></li>
<li><a href="/wiki/POST_(HTTP)" title="POST (HTTP)">POST</a></li>
<li><a href="/wiki/Hypertext_Transfer_Protocol#Request_methods" title="Hypertext Transfer Protocol">PUT</a></li>
<li><a href="/wiki/Hypertext_Transfer_Protocol#Request_methods" title="Hypertext Transfer Protocol">DELETE</a></li>
<li><a href="/wiki/Hypertext_Transfer_Protocol#Request_methods" title="Hypertext Transfer Protocol">TRACE</a></li>
<li><a href="/wiki/Hypertext_Transfer_Protocol#Request_methods" title="Hypertext Transfer Protocol">CONNECT</a></li>
<li><a href="/wiki/Hypertext_Transfer_Protocol#Request_methods" title="Hypertext Transfer Protocol">PATCH</a></li>
</ul>
</td>
</tr>
<tr>
<th style="padding:0.1em"><strong class="selflink">Header fields</strong></th>
</tr>
<tr>
<td style="padding:0 0.1em 0.4em">
<ul>
<li><a href="/wiki/HTTP_cookie" title="HTTP cookie">Cookie</a></li>
<li><a href="/wiki/HTTP_ETag" title="HTTP ETag">ETag</a></li>
<li><a href="/wiki/HTTP_location" title="HTTP location">Location</a></li>
<li><a href="/wiki/HTTP_referer" title="HTTP referer">HTTP referer</a></li>
<li><a href="/wiki/Do_Not_Track" title="Do Not Track">DNT</a></li>
<li><a href="/wiki/X-Forwarded-For" title="X-Forwarded-For">X-Forwarded-For</a></li>
</ul>
</td>
</tr>
<tr>
<th style="padding:0.1em"><a href="/wiki/List_of_HTTP_status_codes" title="List of HTTP status codes">Status codes</a></th>
</tr>
<tr>
<td style="padding:0 0.1em 0.4em">
<ul>
<li><a href="/wiki/HTTP_301" title="HTTP 301">301 Moved Permanently</a></li>
<li><a href="/wiki/HTTP_302" title="HTTP 302">302 Found</a></li>
<li><a href="/wiki/HTTP_303" title="HTTP 303">303 See Other</a></li>
<li><a href="/wiki/HTTP_403" title="HTTP 403">403 Forbidden</a></li>
<li><a href="/wiki/HTTP_404" title="HTTP 404">404 Not Found</a></li>
</ul>
</td>
</tr>
<tr>
<td style="text-align:right;font-size:115%">
<div class="plainlinks hlist navbar mini">
<ul>
<li class="nv-view"><a href="/wiki/Template:HTTP" title="Template:HTTP"><span title="View this template">v</span></a></li>
<li class="nv-talk"><a href="/wiki/Template_talk:HTTP" title="Template talk:HTTP"><span title="Discuss this template">t</span></a></li>
<li class="nv-edit"><a class="external text" href="//en.wikipedia.org/w/index.php?title=Template:HTTP&amp;action=edit"><span title="Edit this template">e</span></a></li>
</ul>
</div>
</td>
</tr>
</tbody></table>
<p><b>HTTP header fields</b> are components of the header section of <a href="/wiki/HTTP_request" title="HTTP request" class="mw-redirect">request</a> and response messages in the <a href="/wiki/Hypertext_Transfer_Protocol" title="Hypertext Transfer Protocol">Hypertext Transfer Protocol</a> (HTTP). They define the operating parameters of an HTTP transaction.</p>
<p></p>
<div id="toc" class="toc">
<div id="toctitle">
<h2>Contents</h2>
<span class="toctoggle">&nbsp;[<a href="#" id="togglelink">hide</a>]&nbsp;</span></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#General_format"><span class="tocnumber">1</span> <span class="toctext">General format</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#Field_names"><span class="tocnumber">2</span> <span class="toctext">Field names</span></a></li>
<li class="toclevel-1 tocsection-3"><a href="#Field_values"><span class="tocnumber">3</span> <span class="toctext">Field values</span></a></li>
<li class="toclevel-1 tocsection-4"><a href="#Size_limits"><span class="tocnumber">4</span> <span class="toctext">Size limits</span></a></li>
<li class="toclevel-1 tocsection-5"><a href="#Request_fields"><span class="tocnumber">5</span> <span class="toctext">Request fields</span></a>
<ul>
<li class="toclevel-2 tocsection-6"><a href="#Common_non-standard_request_fields"><span class="tocnumber">5.1</span> <span class="toctext">Common non-standard request fields</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-7"><a href="#Response_fields"><span class="tocnumber">6</span> <span class="toctext">Response fields</span></a>
<ul>
<li class="toclevel-2 tocsection-8"><a href="#Common_non-standard_response_fields"><span class="tocnumber">6.1</span> <span class="toctext">Common non-standard response fields</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-9"><a href="#Effects_of_selected_fields"><span class="tocnumber">7</span> <span class="toctext">Effects of selected fields</span></a>
<ul>
<li class="toclevel-2 tocsection-10"><a href="#Avoiding_caching"><span class="tocnumber">7.1</span> <span class="toctext">Avoiding caching</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-11"><a href="#See_also"><span class="tocnumber">8</span> <span class="toctext">See also</span></a></li>
<li class="toclevel-1 tocsection-12"><a href="#References"><span class="tocnumber">9</span> <span class="toctext">References</span></a></li>
<li class="toclevel-1 tocsection-13"><a href="#External_links"><span class="tocnumber">10</span> <span class="toctext">External links</span></a></li>
</ul>
</div>
<p></p>
<h2><span class="mw-headline" id="General_format">General format</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=1" title="Edit section: General format">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>The header fields are transmitted after the request or response line, which is the first line of a message. Header fields are colon-separated name-value pairs in clear-text <a href="/wiki/String_(computer_science)" title="String (computer science)">string</a> format, terminated by a carriage return (CR) and line feed (LF) character sequence. The end of the header section is indicated by an empty field, resulting in the transmission of two consecutive CR-LF pairs. Historically, long lines could be folded into multiple lines; continuation lines are indicated by the presence of a space (SP) or horizontal tab (HT) as the first character on the next line. This folding is now deprecated.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span>[</span>1<span>]</span></a></sup></p>
<h2><span class="mw-headline" id="Field_names">Field names</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=2" title="Edit section: Field names">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>A core set of fields is standardized by the <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF) in RFCs 7230, 7231, 7232, 7233, 7234, and 7235. The <a rel="nofollow" class="external text" href="http://www.iana.org/assignments/message-headers/message-headers.xml#perm-headers">permanent registry of header fields</a> and <a rel="nofollow" class="external text" href="http://www.iana.org/assignments/message-headers/message-headers.xml#prov-headers">repository of provisional registrations</a> are maintained by the <a href="/wiki/Internet_Assigned_Numbers_Authority" title="Internet Assigned Numbers Authority">IANA</a>. Additional field names and permissible values may be defined by each application.</p>
<p>Non-standard header fields were conventionally marked by prefixing the field name with <code>X-</code><sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span>[</span>2<span>]</span></a></sup> but this convention was deprecated in June 2012 because of the inconveniences it caused when non-standard fields became standard.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span>[</span>3<span>]</span></a></sup> An earlier restriction on use of <code>Downgraded-</code> was lifted in March 2013.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span>[</span>4<span>]</span></a></sup></p>
<h2><span class="mw-headline" id="Field_values">Field values</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=3" title="Edit section: Field values">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>A few fields can contain comments (i.e. in User-Agent, Server, Via fields), which can be ignored by software.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span>[</span>5<span>]</span></a></sup></p>
<p>Many field values may contain a quality (<i>q</i>) key-value pair, specifying a weight to use in <a href="/wiki/Content_negotiation" title="Content negotiation">content negotiation</a>.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span>[</span>6<span>]</span></a></sup></p>
<h2><span class="mw-headline" id="Size_limits">Size limits</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=4" title="Edit section: Size limits">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>The standard imposes no limits to the size of each header field name or value, or to the number of fields. However, most servers, clients, and proxy software impose some limits for practical and security reasons. For example, the Apache 2.3 server by default limits the size of each field to 8190 bytes, and there can be at most 100 header fields in a single request.<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span>[</span>7<span>]</span></a></sup></p>
<h2><span class="mw-headline" id="Request_fields">Request fields</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=5" title="Edit section: Request fields">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<table class="wikitable sortable jquery-tablesorter" style="width: 100%; clear:right;">
<thead><tr>
<th class="headerSort" tabindex="0" role="columnheader button" title="Sort ascending">Header field name</th>
<th class="unsortable">Description</th>
<th class="unsortable">Example</th>
<th class="headerSort" tabindex="0" role="columnheader button" title="Sort ascending">Status</th>
</tr></thead><tbody>
<tr>
<td>Accept</td>
<td>Content-Types that are acceptable for the response. See <a href="/wiki/Content_negotiation" title="Content negotiation">Content negotiation</a>.</td>
<td><code>Accept: text/plain</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Accept-Charset</td>
<td>Character sets that are acceptable</td>
<td><code>Accept-Charset: utf-8</code></td>
<td>Permanent</td>
</tr>
<tr id="Accept-Encoding">
<td>Accept-Encoding</td>
<td>List of acceptable encodings. See <a href="/wiki/HTTP_compression" title="HTTP compression">HTTP compression</a>.</td>
<td><code>Accept-Encoding: gzip, deflate</code></td>
<td>Permanent</td>
</tr>
<tr id="Accept-Language">
<td>Accept-Language</td>
<td>List of acceptable human languages for response. See <a href="/wiki/Content_negotiation" title="Content negotiation">Content negotiation</a>.</td>
<td><code>Accept-Language: en-US</code></td>
<td>Permanent</td>
</tr>
<tr id="Accept-Datetime">
<td>Accept-Datetime</td>
<td>Acceptable version in time</td>
<td><code>Accept-Datetime: Thu, 31 May 2007 20:35:00 GMT</code></td>
<td>Provisional</td>
</tr>
<tr>
<td>Authorization</td>
<td>Authentication credentials for HTTP authentication</td>
<td><code>Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==</code></td>
<td>Permanent</td>
</tr>
<tr>
<td><a href="/wiki/Cache-Control" title="Cache-Control" class="mw-redirect">Cache-Control</a></td>
<td>Used to specify directives that <i>must</i> be obeyed by all caching mechanisms along the request-response chain</td>
<td><code>Cache-Control: no-cache</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Connection</td>
<td>Control options for the current connection and list of hop-by-hop request fields<sup id="cite_ref-rfc7230_connection_8-0" class="reference"><a href="#cite_note-rfc7230_connection-8"><span>[</span>8<span>]</span></a></sup></td>
<td><code>Connection: keep-alive</code>
<p><code><a href="/wiki/HTTP/1.1_Upgrade_header" title="HTTP/1.1 Upgrade header">Connection: Upgrade</a></code></p>
</td>
<td>Permanent</td>
</tr>
<tr>
<td>Cookie</td>
<td>An <a href="/wiki/HTTP_cookie" title="HTTP cookie">HTTP cookie</a> previously sent by the server with <tt><a href="#innerlink_set-cookie">Set-Cookie</a></tt> (below)</td>
<td><code>Cookie: $Version=1; Skin=new;</code></td>
<td>Permanent: standard</td>
</tr>
<tr id="Content-Length">
<td>Content-Length</td>
<td>The length of the request body in <a href="/wiki/Octet_(computing)" title="Octet (computing)">octets</a> (8-bit bytes)</td>
<td><code>Content-Length: 348</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Content-MD5</td>
<td>A <a href="/wiki/Base64" title="Base64">Base64</a>-encoded binary <a href="/wiki/MD5" title="MD5">MD5</a> sum of the content of the request body</td>
<td><code>Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ==</code></td>
<td>Obsolete<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span>[</span>9<span>]</span></a></sup></td>
</tr>
<tr>
<td>Content-Type</td>
<td>The <a href="/wiki/MIME_type" title="MIME type" class="mw-redirect">MIME type</a> of the body of the request (used with POST and PUT requests)</td>
<td><code>Content-Type: application/x-www-form-urlencoded</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Date</td>
<td>The date and time that the message was sent (in "HTTP-date" format as defined by <a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7231#section-7.1.1.1">RFC 7231 Date/Time Formats</a>)</td>
<td><code>Date: Tue, 15 Nov 1994 08:12:31 GMT</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Expect</td>
<td>Indicates that particular server behaviors are required by the client</td>
<td><code>Expect: 100-continue</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>From</td>
<td>The email address of the user making the request</td>
<td><code>From: [email protected]</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Host</td>
<td>The domain name of the server (for <a href="/wiki/Virtual_hosting" title="Virtual hosting">virtual hosting</a>), and the <a href="/wiki/List_of_TCP_and_UDP_port_numbers" title="List of TCP and UDP port numbers">TCP port</a> number on which the server is listening. The <a href="/wiki/Port_(computer_networking)" title="Port (computer networking)">port</a> number may be omitted if the port is the standard port for the service requested.
<p><sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span>[</span>10<span>]</span></a></sup> Mandatory since HTTP/1.1.</p>
</td>
<td><code>Host: en.wikipedia.org:80</code>
<p><code>Host: en.wikipedia.org</code></p>
</td>
<td>Permanent</td>
</tr>
<tr>
<td>If-Match</td>
<td>Only perform the action if the client supplied entity matches the same entity on the server. This is mainly for methods like PUT to only update a resource if it has not been modified since the user last updated it.</td>
<td><code>If-Match: "737060cd8c284d8af7ad3082f209582d"</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>If-Modified-Since</td>
<td>Allows a <i>304 Not Modified</i> to be returned if content is unchanged</td>
<td><code>If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>If-None-Match</td>
<td>Allows a <i>304 Not Modified</i> to be returned if content is unchanged, see <a href="/wiki/HTTP_ETag" title="HTTP ETag">HTTP ETag</a></td>
<td><code>If-None-Match: "737060cd8c284d8af7ad3082f209582d"</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>If-Range</td>
<td>If the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity</td>
<td><code>If-Range: "737060cd8c284d8af7ad3082f209582d"</code></td>
<td>Permanent</td>
</tr>
<tr>
<td style="white-space:nowrap">If-Unmodified-Since</td>
<td>Only send the response if the entity has not been modified since a specific time.</td>
<td><code>If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Max-Forwards</td>
<td>Limit the number of times the message can be forwarded through proxies or gateways.</td>
<td><code>Max-Forwards: 10</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Origin</td>
<td>Initiates a request for <a href="/wiki/Cross-origin_resource_sharing" title="Cross-origin resource sharing">cross-origin resource sharing</a> (asks server for an 'Access-Control-Allow-Origin' response field) .</td>
<td><code>Origin: http://www.example-social-network.com</code></td>
<td>Permanent: standard</td>
</tr>
<tr>
<td>Pragma</td>
<td>Implementation-specific fields that may have various effects anywhere along the request-response chain.</td>
<td><code><a href="#Avoiding_caching">Pragma: no-cache</a></code></td>
<td>Permanent</td>
</tr>
<tr>
<td style="white-space:nowrap">Proxy-Authorization</td>
<td>Authorization credentials for connecting to a proxy.</td>
<td><code>Proxy-Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==</code></td>
<td>Permanent</td>
</tr>
<tr id="range-request-header">
<td><span id="Range"></span> Range</td>
<td>Request only part of an entity. Bytes are numbered from 0. See <a href="/wiki/Byte_serving" title="Byte serving">Byte serving</a>.</td>
<td><code>Range: bytes=500-999</code></td>
<td>Permanent</td>
</tr>
<tr>
<td><a href="/wiki/HTTP_referer" title="HTTP referer">Referer</a> [<i><a href="/wiki/Sic" title="Sic">sic</a></i>]</td>
<td>This is the address of the previous web page from which a link to the currently requested page was followed. (The word “referrer” has been misspelled in the RFC as well as in most implementations to the point that it has become standard usage and is considered correct terminology)</td>
<td><code>Referer: http://en.wikipedia.org/wiki/Main_Page</code></td>
<td>Permanent</td>
</tr>
<tr id="te-request-header">
<td>TE</td>
<td>The transfer encodings the user agent is willing to accept: the same values as for the response header field Transfer-Encoding can be used, plus the "trailers" value (related to the "<a href="/wiki/Chunked_transfer_encoding" title="Chunked transfer encoding">chunked</a>" transfer method) to notify the server it expects to receive additional fields in the trailer after the last, zero-sized, chunk.</td>
<td><code>TE: trailers, <a href="/wiki/Deflate" title="Deflate" class="mw-redirect">deflate</a></code></td>
<td>Permanent</td>
</tr>
<tr>
<td>User-Agent</td>
<td>The <a href="/wiki/User_agent_string" title="User agent string" class="mw-redirect">user agent string</a> of the user agent</td>
<td><code>User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/21.0</code></td>
<td>Permanent</td>
</tr>
<tr>
<td><a href="/wiki/Upgrade_header" title="Upgrade header" class="mw-redirect">Upgrade</a></td>
<td>Ask the server to upgrade to another protocol.</td>
<td><code>Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Via</td>
<td>Informs the server of proxies through which the request was sent.</td>
<td><code>Via: 1.0 fred, 1.1 example.com (Apache/1.1)</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Warning</td>
<td>A general warning about possible problems with the entity body.</td>
<td><code>Warning: 199 Miscellaneous warning</code></td>
<td>Permanent</td>
</tr>
</tbody><tfoot></tfoot></table>
<h3><span class="mw-headline" id="Common_non-standard_request_fields">Common non-standard request fields</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=6" title="Edit section: Common non-standard request fields">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<table class="wikitable sortable jquery-tablesorter" style="width: 100%; clear:right;">
<thead><tr>
<th class="headerSort" tabindex="0" role="columnheader button" title="Sort ascending">Field name</th>
<th class="unsortable">Description</th>
<th class="unsortable">Example</th>
</tr></thead><tbody>
<tr id="Requested-With">
<td style="white-space:nowrap">X-Requested-With</td>
<td>mainly used to identify <a href="/wiki/Ajax_(programming)" title="Ajax (programming)">Ajax</a> requests. Most <a href="/wiki/JavaScript_framework" title="JavaScript framework" class="mw-redirect">JavaScript frameworks</a> send this field with value of <code>XMLHttpRequest</code></td>
<td><code>X-Requested-With: XMLHttpRequest</code></td>
</tr>
<tr>
<td><a href="/wiki/Do_Not_Track" title="Do Not Track">DNT</a><sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span>[</span>11<span>]</span></a></sup></td>
<td>Requests a web application to disable their tracking of a user. This is Mozilla's version of the X-Do-Not-Track header field (since <a href="/wiki/Mozilla_Firefox_4" title="Mozilla Firefox 4" class="mw-redirect">Firefox 4.0</a> Beta 11). <a href="/wiki/Safari_(web_browser)" title="Safari (web browser)">Safari</a> and <a href="/wiki/Internet_Explorer_9" title="Internet Explorer 9">IE9</a> also have support for this field.<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span>[</span>12<span>]</span></a></sup> On March 7, 2011, a draft proposal was submitted to IETF.<sup id="cite_ref-13" class="reference"><a href="#cite_note-13"><span>[</span>13<span>]</span></a></sup> The <a href="/wiki/World_Wide_Web_Consortium" title="World Wide Web Consortium">W3C</a> Tracking Protection Working Group is producing a specification.<sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span>[</span>14<span>]</span></a></sup></td>
<td><code>DNT: 1 (Do Not Track Enabled)</code>
<p><code>DNT: 0 (Do Not Track Disabled)</code></p>
</td>
</tr>
<tr>
<td style="white-space:nowrap"><a href="/wiki/X-Forwarded-For" title="X-Forwarded-For">X-Forwarded-For</a><sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span>[</span>15<span>]</span></a></sup></td>
<td>a <a href="/wiki/De_facto_standard" title="De facto standard"><i>de facto</i> standard</a> for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer</td>
<td><code>X-Forwarded-For: client1, proxy1, proxy2</code>
<p><code>X-Forwarded-For: 129.78.138.66, 129.78.64.103</code></p>
</td>
</tr>
<tr>
<td>X-Forwarded-Host<sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span>[</span>16<span>]</span></a></sup></td>
<td>a <a href="/wiki/De_facto_standard" title="De facto standard"><i>de facto</i> standard</a> for identifying the original host requested by the client in the <code>Host</code> HTTP request header, since the host name and/or port of the reverse proxy (load balancer) may differ from the origin server handling the request.</td>
<td><code>X-Forwarded-Host: en.wikipedia.org:80</code>
<p><code>X-Forwarded-Host: en.wikipedia.org</code></p>
</td>
</tr>
<tr>
<td>X-Forwarded-Proto<sup id="cite_ref-17" class="reference"><a href="#cite_note-17"><span>[</span>17<span>]</span></a></sup></td>
<td>a <a href="/wiki/De_facto_standard" title="De facto standard"><i>de facto</i> standard</a> for identifying the originating protocol of an HTTP request, since a reverse proxy (load balancer) may communicate with a web server using HTTP even if the request to the reverse proxy is HTTPS. An alternative form of the header (X-ProxyUser-Ip) is used by Google clients talking to Google servers.</td>
<td><code>X-Forwarded-Proto: https</code></td>
</tr>
<tr>
<td>Front-End-Https<sup id="cite_ref-18" class="reference"><a href="#cite_note-18"><span>[</span>18<span>]</span></a></sup></td>
<td>Non-standard header field used by Microsoft applications and load-balancers</td>
<td><code>Front-End-Https: on</code></td>
</tr>
<tr>
<td>X-Http-Method-Override<sup id="cite_ref-19" class="reference"><a href="#cite_note-19"><span>[</span>19<span>]</span></a></sup></td>
<td>Requests a web application override the method specified in the request (typically POST) with the method given in the header field (typically PUT or DELETE). Can be used when a user agent or firewall prevents PUT or DELETE methods from being sent directly (note that this either a bug in the software component, which ought to be fixed, or an intentional configuration, in which case bypassing it may be the wrong thing to do).</td>
<td><code>X-HTTP-Method-Override: DELETE</code></td>
</tr>
<tr>
<td>X-ATT-DeviceId<sup id="cite_ref-20" class="reference"><a href="#cite_note-20"><span>[</span>20<span>]</span></a></sup></td>
<td>Allows easier parsing of the MakeModel/Firmware that is usually found in the User-Agent String of AT&amp;T Devices</td>
<td><code>X-Att-Deviceid: GT-P7320/P7320XXLPG</code></td>
</tr>
<tr>
<td>X-Wap-Profile<sup id="cite_ref-21" class="reference"><a href="#cite_note-21"><span>[</span>21<span>]</span></a></sup></td>
<td>Links to an XML file on the Internet with a full description and details about the device currently connecting. In the example to the right is an XML file for an AT&amp;T Samsung Galaxy S2.</td>
<td><code>x-wap-profile: <a rel="nofollow" class="external free" href="http://wap.samsungmobile.com/uaprof/SGH-I777.xml">http://wap.samsungmobile.com/uaprof/SGH-I777.xml</a></code></td>
</tr>
<tr>
<td>Proxy-Connection<sup id="cite_ref-22" class="reference"><a href="#cite_note-22"><span>[</span>22<span>]</span></a></sup></td>
<td>Implemented as a misunderstanding of the HTTP specifications. Common because of mistakes in implementations of early HTTP versions. Has exactly the same functionality as standard Connection field.</td>
<td><code>Proxy-Connection: keep-alive</code></td>
</tr>
<tr>
<td>X-UIDH<sup id="cite_ref-23" class="reference"><a href="#cite_note-23"><span>[</span>23<span>]</span></a></sup><sup id="cite_ref-24" class="reference"><a href="#cite_note-24"><span>[</span>24<span>]</span></a></sup><sup id="cite_ref-25" class="reference"><a href="#cite_note-25"><span>[</span>25<span>]</span></a></sup></td>
<td>Server-side <a href="/wiki/Deep_packet_inspection" title="Deep packet inspection">deep packet insertion</a> of a unique ID identifying customers of <a href="/wiki/Verizon_Wireless" title="Verizon Wireless">Verizon Wireless</a>; also known as "perma-cookie" or "supercookie"</td>
<td><code>X-UIDH: ...</code></td>
</tr>
<tr>
<td>X-Csrf-Token<sup id="cite_ref-26" class="reference"><a href="#cite_note-26"><span>[</span>26<span>]</span></a></sup></td>
<td>Used to prevent <a href="/wiki/Cross-site_request_forgery" title="Cross-site request forgery">cross-site request forgery</a>. Alternative header names are: <code>X-CSRFToken</code><sup id="cite_ref-27" class="reference"><a href="#cite_note-27"><span>[</span>27<span>]</span></a></sup> and <code>X-XSRF-TOKEN</code><sup id="cite_ref-28" class="reference"><a href="#cite_note-28"><span>[</span>28<span>]</span></a></sup></td>
<td><code>X-Csrf-Token: i8XNjC4b8KVok4uw5RftR38Wgp2BFwql</code></td>
</tr>
</tbody><tfoot></tfoot></table>
<h2><span class="mw-headline" id="Response_fields">Response fields</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=7" title="Edit section: Response fields">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<table class="wikitable sortable jquery-tablesorter" style="width: 100%">
<thead><tr>
<th class="headerSort" tabindex="0" role="columnheader button" title="Sort ascending">Field name</th>
<th class="unsortable">Description</th>
<th class="unsortable">Example</th>
<th class="headerSort" tabindex="0" role="columnheader button" title="Sort ascending">Status</th>
</tr></thead><tbody>
<tr>
<td>Access-Control-Allow-Origin</td>
<td>Specifying which web sites can participate in <a href="/wiki/Cross-origin_resource_sharing" title="Cross-origin resource sharing">cross-origin resource sharing</a></td>
<td><code>Access-Control-Allow-Origin: *</code></td>
<td>Provisional</td>
</tr>
<tr id="accept-patch-response-header">
<td>Accept-Patch<sup id="cite_ref-29" class="reference"><a href="#cite_note-29"><span>[</span>29<span>]</span></a></sup></td>
<td>Specifies which patch document formats this server supports</td>
<td><code>Accept-Patch: text/example;charset=utf-8</code></td>
<td>Permanent</td>
</tr>
<tr id="accept-ranges-response-header">
<td>Accept-Ranges</td>
<td>What partial content range types this server supports</td>
<td><code>Accept-Ranges: bytes</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Age</td>
<td>The age the object has been in a <a href="/wiki/Proxy_cache" title="Proxy cache" class="mw-redirect">proxy cache</a> in seconds</td>
<td><code>Age: 12</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Allow</td>
<td>Valid actions for a specified resource. To be used for a <i>405 Method not allowed</i></td>
<td><code>Allow: GET, HEAD</code></td>
<td>Permanent</td>
</tr>
<tr>
<td><a href="/wiki/Cache-Control" title="Cache-Control" class="mw-redirect">Cache-Control</a></td>
<td>Tells all caching mechanisms from server to client whether they may cache this object. It is measured in seconds</td>
<td><code>Cache-Control: max-age=3600</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Connection</td>
<td>Control options for the current connection and list of hop-by-hop response fields<sup id="cite_ref-rfc7230_connection_8-1" class="reference"><a href="#cite_note-rfc7230_connection-8"><span>[</span>8<span>]</span></a></sup></td>
<td><code>Connection: close</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Content-Disposition<sup id="cite_ref-30" class="reference"><a href="#cite_note-30"><span>[</span>30<span>]</span></a></sup></td>
<td>An opportunity to raise a "File Download" dialogue box for a known MIME type with binary format or suggest a filename for dynamic content. Quotes are necessary with special characters.</td>
<td><code>Content-Disposition: attachment; filename="fname.ext"</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Content-Encoding</td>
<td>The type of encoding used on the data. See <a href="/wiki/HTTP_compression" title="HTTP compression">HTTP compression</a>.</td>
<td><code>Content-Encoding: gzip</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Content-Language</td>
<td>The natural language or languages of the intended audience for the enclosed content<sup id="cite_ref-31" class="reference"><a href="#cite_note-31"><span>[</span>31<span>]</span></a></sup></td>
<td><code>Content-Language: da</code></td>
<td>Permanent</td>
</tr>
<tr id="content-length-response-header">
<td>Content-Length</td>
<td>The length of the response body in <a href="/wiki/Octet_(computing)" title="Octet (computing)">octets</a> (8-bit bytes)</td>
<td><code>Content-Length: 348</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Content-Location</td>
<td>An alternate location for the returned data</td>
<td><code>Content-Location: /index.htm</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Content-MD5</td>
<td>A <a href="/wiki/Base64" title="Base64">Base64</a>-encoded binary <a href="/wiki/MD5" title="MD5">MD5</a> sum of the content of the response</td>
<td><code>Content-MD5: Q2hlY2sgSW50ZWdyaXR5IQ==</code></td>
<td>Obsolete<sup id="cite_ref-32" class="reference"><a href="#cite_note-32"><span>[</span>32<span>]</span></a></sup></td>
</tr>
<tr id="content-range-response-header">
<td>Content-Range</td>
<td>Where in a full body message this partial message belongs</td>
<td><code>Content-Range: bytes 21010-47021/47022</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Content-Type</td>
<td>The <a href="/wiki/MIME_type" title="MIME type" class="mw-redirect">MIME type</a> of this content</td>
<td><code>Content-Type: text/html; charset=utf-8</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Date</td>
<td>The date and time that the message was sent (in "HTTP-date" format as defined by <a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc7231">RFC 7231</a>)</td>
<td><code>Date: Tue, 15 Nov 1994 08:12:31 GMT</code></td>
<td>Permanent</td>
</tr>
<tr>
<td><a href="/wiki/HTTP_ETag" title="HTTP ETag">ETag</a></td>
<td>An identifier for a specific version of a resource, often a <a href="/wiki/Message_digest" title="Message digest" class="mw-redirect">message digest</a></td>
<td><code>ETag: "737060cd8c284d8af7ad3082f209582d"</code></td>
<td>Permanent</td>
</tr>
<tr id="Expires">
<td>Expires</td>
<td>Gives the date/time after which the response is considered stale (in "HTTP-date" format as defined by <a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc7231">RFC 7231</a>)</td>
<td><code>Expires: Thu, 01 Dec 1994 16:00:00 GMT</code></td>
<td>Permanent: standard</td>
</tr>
<tr>
<td>Last-Modified</td>
<td>The last modified date for the requested object (in "HTTP-date" format as defined by <a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc7231">RFC 7231</a>)</td>
<td><code>Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Link</td>
<td>Used to express a typed relationship with another resource, where the relation type is defined by <a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc5988">RFC 5988</a></td>
<td><code>Link: &lt;/feed&gt;; rel="alternate"</code><sup id="cite_ref-google_canonical_33-0" class="reference"><a href="#cite_note-google_canonical-33"><span>[</span>33<span>]</span></a></sup></td>
<td>Permanent</td>
</tr>
<tr>
<td><a href="/wiki/HTTP_location" title="HTTP location">Location</a></td>
<td>Used in <a href="/wiki/URL_redirection" title="URL redirection">redirection</a>, or when a new resource has been created.</td>
<td><code>Location: http://www.w3.org/pub/WWW/People.html</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>P3P</td>
<td>This field is supposed to set <a href="/wiki/P3P" title="P3P">P3P</a> policy, in the form of <code>P3P:CP="your_compact_policy"</code>. However, P3P did not take off,<sup id="cite_ref-34" class="reference"><a href="#cite_note-34"><span>[</span>34<span>]</span></a></sup> most browsers have never fully implemented it, a lot of websites set this field with fake policy text, that was enough to fool browsers the existence of P3P policy and grant permissions for <a href="/wiki/HTTP_cookie#Third-party_cookie" title="HTTP cookie">third party cookies</a>.</td>
<td><code>P3P: CP="This is not a P3P policy! See http://www.google.com/support/accounts/bin/answer.py?hl=en&amp;answer=151657 for more info."</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Pragma</td>
<td>Implementation-specific fields that may have various effects anywhere along the request-response chain.</td>
<td><code>Pragma: no-cache</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Proxy-Authenticate</td>
<td>Request authentication to access the proxy.</td>
<td><code>Proxy-Authenticate: Basic</code></td>
<td>Permanent</td>
</tr>
<tr id="PKP">
<td>Public-Key-Pins<sup id="cite_ref-35" class="reference"><a href="#cite_note-35"><span>[</span>35<span>]</span></a></sup></td>
<td><a href="/wiki/HTTP_Public_Key_Pinning" title="HTTP Public Key Pinning">HTTP Public Key Pinning</a>, announces hash of website's authentic <a href="/wiki/Transport_Layer_Security" title="Transport Layer Security">TLS</a> certificate</td>
<td><code>Public-Key-Pins: max-age=2592000; pin-sha256="E9CZ9INDbd+2eRQozYqqbQ2yXLVKB9+xcprMF+44U1g=";</code></td>
<td>Permanent</td>
</tr>
<tr id="Refresh">
<td><a href="/wiki/HTTP_refresh" title="HTTP refresh" class="mw-redirect">Refresh</a></td>
<td>Used in redirection, or when a new resource has been created. This refresh redirects after 5 seconds.</td>
<td><code>Refresh: 5; url=http://www.w3.org/pub/WWW/People.html</code></td>
<td>Proprietary and non-standard: a header extension introduced by Netscape and supported by most web browsers.</td>
</tr>
<tr>
<td>Retry-After</td>
<td>If an entity is temporarily unavailable, this instructs the client to try again later. Value could be a specified period of time (in seconds) or a HTTP-date.<sup id="cite_ref-36" class="reference"><a href="#cite_note-36"><span>[</span>36<span>]</span></a></sup></td>
<td>
<ul>
<li>Example 1: <code>Retry-After: 120</code></li>
<li>Example 2: <code>Retry-After: Fri, 07 Nov 2014 23:59:59 GMT</code></li>
</ul>
</td>
<td>
<p>Permanent</p>
</td>
</tr>
<tr>
<td>Server</td>
<td>A name for the server</td>
<td><code>Server: Apache/2.4.1 (Unix)</code></td>
<td>Permanent</td>
</tr>
<tr>
<td id="innerlink_set-cookie">Set-Cookie</td>
<td>An <a href="/wiki/HTTP_cookie" title="HTTP cookie">HTTP cookie</a></td>
<td><code>Set-Cookie: UserID=JohnDoe; Max-Age=3600; Version=1</code></td>
<td>Permanent: standard</td>
</tr>
<tr>
<td>Status</td>
<td><a href="/wiki/Common_Gateway_Interface" title="Common Gateway Interface">CGI</a> header field specifying the <a href="/wiki/HTTP_status" title="HTTP status" class="mw-redirect">status</a> of the HTTP response. Normal HTTP responses use a separate "Status-Line" instead, defined by <a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc7230">RFC 7230</a>.<sup id="cite_ref-37" class="reference"><a href="#cite_note-37"><span>[</span>37<span>]</span></a></sup></td>
<td><code>Status: 200 OK</code></td>
<td>Not listed as a <a rel="nofollow" class="external text" href="http://www.iana.org/assignments/message-headers/message-headers.xml">registered field name</a></td>
</tr>
<tr>
<td style="white-space:nowrap"><a href="/wiki/HTTP_Strict_Transport_Security" title="HTTP Strict Transport Security">Strict-Transport-Security</a></td>
<td>A HSTS Policy informing the HTTP client how long to cache the HTTPS only policy and whether this applies to subdomains.</td>
<td><code>Strict-Transport-Security: max-age=16070400; includeSubDomains</code></td>
<td>Permanent: standard</td>
</tr>
<tr id="trailer-response-header">
<td>Trailer</td>
<td>The Trailer general field value indicates that the given set of header fields is present in the trailer of a message encoded with <a href="/wiki/Chunked_transfer_coding" title="Chunked transfer coding" class="mw-redirect">chunked transfer coding</a>.</td>
<td><code>Trailer: Max-Forwards</code></td>
<td>Permanent</td>
</tr>
<tr id="transfer-encoding-response-header">
<td>Transfer-Encoding</td>
<td>The form of encoding used to safely transfer the entity to the user. <a rel="nofollow" class="external text" href="http://www.iana.org/assignments/http-parameters">Currently defined methods</a> are: <a href="/wiki/Chunked_transfer_encoding" title="Chunked transfer encoding">chunked</a>, compress, deflate, gzip, identity.</td>
<td><code>Transfer-Encoding: chunked</code></td>
<td>Permanent</td>
</tr>
<tr>
<td><a href="/wiki/Upgrade_header" title="Upgrade header" class="mw-redirect">Upgrade</a></td>
<td>Ask the client to upgrade to another protocol.</td>
<td><code>Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Vary</td>
<td>Tells downstream proxies how to match future request headers to decide whether the cached response can be used rather than requesting a fresh one from the origin server.</td>
<td><code>Vary: *</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Via</td>
<td>Informs the client of proxies through which the response was sent.</td>
<td><code>Via: 1.0 fred, 1.1 example.com (Apache/1.1)</code></td>
<td>Permanent</td>
</tr>
<tr>
<td>Warning</td>
<td>A general warning about possible problems with the entity body.</td>
<td><code>Warning: 199 Miscellaneous warning</code></td>
<td>Permanent</td>
</tr>
<tr id="www-authenticate-response-header">
<td>WWW-Authenticate</td>
<td>Indicates the authentication scheme that should be used to access the requested entity.</td>
<td><code>WWW-Authenticate: Basic</code></td>
<td>Permanent</td>
</tr>
<tr id="Frame-Options">
<td>X-Frame-Options<sup id="cite_ref-38" class="reference"><a href="#cite_note-38"><span>[</span>38<span>]</span></a></sup></td>
<td><a href="/wiki/Clickjacking" title="Clickjacking">Clickjacking</a> protection: <tt>deny</tt> - no rendering within a frame, <tt>sameorigin</tt> - no rendering if origin mismatch, <tt>allow-from</tt> - allow from specified location, <tt>allowall</tt> - non-standard, allow from any location</td>
<td><code>X-Frame-Options: deny</code></td>
<td>Obsolete<sup id="cite_ref-39" class="reference"><a href="#cite_note-39"><span>[</span>39<span>]</span></a></sup></td>
</tr>
</tbody><tfoot></tfoot></table>
<h3><span class="mw-headline" id="Common_non-standard_response_fields">Common non-standard response fields</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=8" title="Edit section: Common non-standard response fields">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<table class="wikitable sortable jquery-tablesorter" style="width: 100%; clear:right;">
<thead><tr>
<th class="headerSort" tabindex="0" role="columnheader button" title="Sort ascending">Field name</th>
<th class="unsortable">Description</th>
<th class="unsortable">Example</th>
</tr></thead><tbody>
<tr>
<td>X-XSS-Protection<sup id="cite_ref-40" class="reference"><a href="#cite_note-40"><span>[</span>40<span>]</span></a></sup></td>
<td><a href="/wiki/Cross-site_scripting" title="Cross-site scripting">Cross-site scripting</a> (XSS) filter</td>
<td><code>X-XSS-Protection: 1; mode=block</code></td>
</tr>
<tr>
<td>Content-Security-Policy, <i>X-Content-Security-Policy</i>, <i>X-WebKit-CSP</i><sup id="cite_ref-41" class="reference"><a href="#cite_note-41"><span>[</span>41<span>]</span></a></sup></td>
<td><a href="/wiki/Content_Security_Policy" title="Content Security Policy">Content Security Policy</a> definition.</td>
<td><code>X-WebKit-CSP: default-src 'self'</code></td>
</tr>
<tr>
<td style="white-space:nowrap">X-Content-Type-Options<sup id="cite_ref-42" class="reference"><a href="#cite_note-42"><span>[</span>42<span>]</span></a></sup></td>
<td>The only defined value, "nosniff", prevents <a href="/wiki/Internet_Explorer" title="Internet Explorer">Internet Explorer</a> from MIME-sniffing a response away from the declared content-type. This also applies to <a href="/wiki/Google_Chrome" title="Google Chrome">Google Chrome</a>, when downloading extensions.<sup id="cite_ref-43" class="reference"><a href="#cite_note-43"><span>[</span>43<span>]</span></a></sup></td>
<td><code>X-Content-Type-Options: nosniff</code></td>
</tr>
<tr id="Powered-By">
<td>X-Powered-By<sup id="cite_ref-44" class="reference"><a href="#cite_note-44"><span>[</span>44<span>]</span></a></sup></td>
<td>specifies the technology (e.g. ASP.NET, PHP, JBoss) supporting the web application (version details are often in <code>X-Runtime</code>, <code>X-Version</code>, or <code>X-AspNet-Version</code>)</td>
<td><code>X-Powered-By: PHP/5.4.0</code></td>
</tr>
<tr>
<td>X-UA-Compatible<sup id="cite_ref-45" class="reference"><a href="#cite_note-45"><span>[</span>45<span>]</span></a></sup></td>
<td>Recommends the preferred rendering engine (often a backward-compatibility mode) to use to display the content. Also used to activate <a href="/wiki/Chrome_Frame" title="Chrome Frame" class="mw-redirect">Chrome Frame</a> in Internet Explorer.</td>
<td><code>X-UA-Compatible: IE=EmulateIE7</code><br>
<code>X-UA-Compatible: IE=edge</code><br>
<code>X-UA-Compatible: Chrome=1</code></td>
</tr>
<tr>
<td>X-Content-Duration<sup id="cite_ref-46" class="reference"><a href="#cite_note-46"><span>[</span>46<span>]</span></a></sup></td>
<td>Provide the duration of the audio or video in seconds; only supported by Gecko browsers</td>
<td><code>X-Content-Duration: 42.666</code></td>
</tr>
</tbody><tfoot></tfoot></table>
<h2><span class="mw-headline" id="Effects_of_selected_fields">Effects of selected fields</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=9" title="Edit section: Effects of selected fields">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<h3><span class="mw-headline" id="Avoiding_caching">Avoiding caching</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=10" title="Edit section: Avoiding caching">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>If a web server responds with <code>Cache-Control: no-cache</code> then a web browser or other <a href="/wiki/HTTP_cache" title="HTTP cache" class="mw-redirect">caching system</a> (intermediate proxies) must not use the response to satisfy subsequent responses without first checking with the originating server (this process is called validation). This header field is part of HTTP version 1.1, and is ignored by some caches and browsers. It may be simulated by setting the <code>Expires</code> HTTP version 1.0 header field value to a time earlier than the response time. Notice that no-cache is not instructing the browser or proxies about whether or not to cache the content. It just tells the browser and proxies to validate the cache content with the server before using it (this is done by using if-Modified-Since, If-Unmodified-Since, If-Match, If-None-Match attributes mentioned above). Sending a no-cache value thus instructs a browser or proxy to not use the cache contents merely based on "freshness criteria" of the cache content. Another common way to prevent old content from being shown to the user without validation is <code>Cache-Control: max-age=0</code>. This instructs the user agent that the content is stale and should be validated before use.</p>
<p>The header field <code>Cache-Control: no-store</code> is intended to instruct a browser application to make a best effort not to write it to disk (i.e not to cache it).</p>
<p>The request that a resource should not be cached is no guarantee that it will not be written to disk. In particular, the HTTP/1.1 definition draws a distinction between history stores and caches. If the user navigates back to a previous page a browser may still show you a page that has been stored on disk in the history store. This is correct behavior according to the specification. Many user agents show different behavior in loading pages from the history store or cache depending on whether the protocol is HTTP or HTTPS.</p>
<p>The <code>Cache-Control: no-cache</code> HTTP/1.1 header field is also intended for use in requests made by the client. It is a means for the browser to tell the server and any intermediate caches that it wants a fresh version of the resource. The <code>Pragma: no-cache</code> header field, defined in the HTTP/1.0 spec, has the same purpose. It, however, is only defined for the request header. Its meaning in a response header is not specified.<sup id="cite_ref-47" class="reference"><a href="#cite_note-47"><span>[</span>47<span>]</span></a></sup> The behavior of <code>Pragma: no-cache</code> in a response is implementation specific. While some user agents do pay attention to this field in responses,<sup id="cite_ref-Q234067_48-0" class="reference"><a href="#cite_note-Q234067-48"><span>[</span>48<span>]</span></a></sup> the HTTP/1.1 RFC specifically warns against relying on this behavior.</p>
<h2><span class="mw-headline" id="See_also">See also</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=11" title="Edit section: See also">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<ul>
<li><a href="/wiki/HTTP_header_injection" title="HTTP header injection">HTTP header injection</a></li>
<li><a href="/wiki/HTTP_ETag" title="HTTP ETag">HTTP ETag</a></li>
<li><a href="/wiki/List_of_HTTP_status_codes" title="List of HTTP status codes">List of HTTP status codes</a></li>
</ul>
<h2><span class="mw-headline" id="References">References</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=12" title="Edit section: References">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<div class="reflist references-column-width" style="-moz-column-width: 30em; -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;">
<ol class="references">
<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7230#section-3.2.4">"Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"</a>. ietf.org<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-07-23</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hypertext+Transfer+Protocol+%28HTTP%2F1.1%29%3A+Message+Syntax+and+Routing&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7230%23section-3.2.4&amp;rft.pub=ietf.org&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web">Simtec Limited. <a rel="nofollow" class="external text" href="http://www.httpwatch.com/httpgallery/headers/">"2. HTTP Headers"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2010-09-10</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.aulast=Simtec+Limited&amp;rft.au=Simtec+Limited&amp;rft.btitle=2.+HTTP+Headers&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fwww.httpwatch.com%2Fhttpgallery%2Fheaders%2F&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web">Internet Engineering Task Force (2012-06-01). <a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc6648">"RFC 6648"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2012-11-12</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.au=Internet+Engineering+Task+Force&amp;rft.aulast=Internet+Engineering+Task+Force&amp;rft.btitle=RFC+6648&amp;rft.date=2012-06-01&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc6648&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://www.iana.org/assignments/message-headers/message-headers.xml">"Message Headers"</a>. Iana.org. 2014-06-11<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-06-12</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Message+Headers&amp;rft.date=2014-06-11&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fwww.iana.org%2Fassignments%2Fmessage-headers%2Fmessage-headers.xml&amp;rft.pub=Iana.org&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7230#section-3.2.6">"Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"</a>. itef.org<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-07-24</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hypertext+Transfer+Protocol+%28HTTP%2F1.1%29%3A+Message+Syntax+and+Routing&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7230%23section-3.2.6&amp;rft.pub=itef.org&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7231#section-5.3.1">"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content"</a>. ietf.org<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-07-24</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hypertext+Transfer+Protocol+%28HTTP%2F1.1%29%3A+Semantics+and+Content&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7231%23section-5.3.1&amp;rft.pub=ietf.org&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120509104709/https://httpd.apache.org/docs/2.3/mod/core.html#limitrequestfieldsize">"core - Apache HTTP Server"</a>. Httpd.apache.org. Archived from <a rel="nofollow" class="external text" href="http://httpd.apache.org/docs/2.3/mod/core.html#limitrequestfieldsize">the original</a> on 2012-05-09<span class="reference-accessdate">. Retrieved <span class="nowrap">2012-03-13</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=core+-+Apache+HTTP+Server&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fhttpd.apache.org%2Fdocs%2F2.3%2Fmod%2Fcore.html%23limitrequestfieldsize&amp;rft.pub=Httpd.apache.org&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-rfc7230_connection-8"><span class="mw-cite-backlink">^ <a href="#cite_ref-rfc7230_connection_8-0"><span class="cite-accessibility-label">Jump up to: </span><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-rfc7230_connection_8-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7230#section-6.1">"Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"</a>. <a href="/wiki/IETF" title="IETF" class="mw-redirect">IETF</a>. June 2014<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-12-19</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hypertext+Transfer+Protocol+%28HTTP%2F1.1%29%3A+Message+Syntax+and+Routing&amp;rft.date=June+2014&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7230%23section-6.1&amp;rft.pub=IETF&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7231#appendix-B">"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2015-06-03</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hypertext+Transfer+Protocol+%28HTTP%2F1.1%29%3A+Semantics+and+Content&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7231%23appendix-B&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7230#section-5.4">"Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"</a>. <a href="/wiki/IETF" title="IETF" class="mw-redirect">IETF</a>. June 2014<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-07-24</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hypertext+Transfer+Protocol+%28HTTP%2F1.1%29%3A+Message+Syntax+and+Routing&amp;rft.date=June+2014&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7230%23section-5.4&amp;rft.pub=IETF&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://blog.sidstamm.com/2011/01/try-out-do-not-track-http-header.html">"Try out the "Do Not Track" HTTP header"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2011-01-31</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Try+out+the+%22Do+Not+Track%22+HTTP+header&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fblog.sidstamm.com%2F2011%2F01%2Ftry-out-do-not-track-http-header.html&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://blogs.msdn.com/b/ie/archive/2011/03/14/web-tracking-protection-minimum-standards-and-opportunities-to-innovate.aspx">"Web Tracking Protection: Minimum Standards and Opportunities to Innovate"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2011-03-24</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Web+Tracking+Protection%3A+Minimum+Standards+and+Opportunities+to+Innovate&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fblogs.msdn.com%2Fb%2Fie%2Farchive%2F2011%2F03%2F14%2Fweb-tracking-protection-minimum-standards-and-opportunities-to-innovate.aspx&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-13"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text">IETF <a rel="nofollow" class="external text" href="http://tools.ietf.org/html/draft-mayer-do-not-track-00">Do Not Track: A Universal Third-Party Web Tracking Opt Out</a> March 7, 2011</span></li>
<li id="cite_note-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-14"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text">W3C <a rel="nofollow" class="external text" href="http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html">Tracking Preference Expression (DNT)</a>, January 26, 2012</span></li>
<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web">Amos Jeffries (2010-07-02). <a rel="nofollow" class="external text" href="http://wiki.squid-cache.org/SquidFaq/ConfiguringSquid#head-3518b69c63e221cc3cd7885415e365ffaf3dd27f">"SquidFaq/ConfiguringSquid - Squid Web Proxy Wiki"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2009-09-10</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.au=Amos+Jeffries&amp;rft.aulast=Amos+Jeffries&amp;rft.btitle=SquidFaq%2FConfiguringSquid+-+Squid+Web+Proxy+Wiki&amp;rft.date=2010-07-02&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fwiki.squid-cache.org%2FSquidFaq%2FConfiguringSquid%23head-3518b69c63e221cc3cd7885415e365ffaf3dd27f&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web">The Apache Software Foundation. <a rel="nofollow" class="external text" href="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#x-headers">"mod_proxy - Apache HTTP Server Version 2.2"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2014-11-12</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.aulast=The+Apache+Software+Foundation&amp;rft.au=The+Apache+Software+Foundation&amp;rft.btitle=mod_proxy+-+Apache+HTTP+Server+Version+2.2&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fhttpd.apache.org%2Fdocs%2F2.2%2Fmod%2Fmod_proxy.html%23x-headers&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-17"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web">Dave Steinberg (2007-04-10). <a rel="nofollow" class="external text" href="http://www.geekisp.com/faq/6_65_en.html">"How do I adjust my SSL site to work with GeekISP's loadbalancer?"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2010-09-30</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.au=Dave+Steinberg&amp;rft.aulast=Dave+Steinberg&amp;rft.btitle=How+do+I+adjust+my+SSL+site+to+work+with+GeekISP%27s+loadbalancer%3F&amp;rft.date=2007-04-10&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fwww.geekisp.com%2Ffaq%2F6_65_en.html&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-18"><span class="mw-cite-backlink"><b><a href="#cite_ref-18"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://technet.microsoft.com/en-us/library/aa997519(v=exchg.65).aspx">"Helping to Secure Communication: Client to Front-End Server"</a>. 2006-07-27<span class="reference-accessdate">. Retrieved <span class="nowrap">2012-04-23</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Helping+to+Secure+Communication%3A+Client+to+Front-End+Server&amp;rft.date=2006-07-27&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Faa997519%28v%3Dexchg.65%29.aspx&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-19"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://opensocial.github.io/spec/2.5.1/Core-API-Server.xml#rfc.section.2.1.1.1">"OpenSocial Core API Server Specification 2.5.1"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2014-10-08</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=OpenSocial+Core+API+Server+Specification+2.5.1&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fopensocial.github.io%2Fspec%2F2.5.1%2FCore-API-Server.xml%23rfc.section.2.1.1.1&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-20"><span class="mw-cite-backlink"><b><a href="#cite_ref-20"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://developer.att.com/developer/forward.jsp?passedItemId=5300270">"ATT Device ID"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2012-01-14</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=ATT+Device+ID&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fdeveloper.att.com%2Fdeveloper%2Fforward.jsp%3FpassedItemId%3D5300270&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-21"><span class="mw-cite-backlink"><b><a href="#cite_ref-21"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://www.developershome.com/wap/detection/detection.asp?page=profileHeader">"WAP Profile"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2012-01-14</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=WAP+Profile&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fwww.developershome.com%2Fwap%2Fdetection%2Fdetection.asp%3Fpage%3DprofileHeader&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-22"><span class="mw-cite-backlink"><b><a href="#cite_ref-22"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/web-proxy-connection-header.html">"The Proxy-Connection: header is a mistake in how some web browsers use HTTP."</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2014-01-02</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=The+Proxy-Connection%3A+header+is+a+mistake+in+how+some+web+browsers+use+HTTP.&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fhomepage.ntlworld.com%2Fjonathan.deboynepollard%2FFGA%2Fweb-proxy-connection-header.html&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-23"><span class="mw-cite-backlink"><b><a href="#cite_ref-23"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="https://www.eff.org/deeplinks/2014/11/verizon-x-uidh">"Verizon Injecting Perma-Cookies to Track Mobile Customers, Bypassing Privacy Controls"</a>. <a href="/wiki/Electronic_Frontier_Foundation" title="Electronic Frontier Foundation">Electronic Frontier Foundation</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2014-01-19</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Verizon+Injecting+Perma-Cookies+to+Track+Mobile+Customers%2C+Bypassing+Privacy+Controls&amp;rft.genre=book&amp;rft_id=https%3A%2F%2Fwww.eff.org%2Fdeeplinks%2F2014%2F11%2Fverizon-x-uidh&amp;rft.pub=Electronic+Frontier+Foundation&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-24"><span class="mw-cite-backlink"><b><a href="#cite_ref-24"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://lessonslearned.org/sniff">"Checking known AT&amp;T, Verizon, Sprint, Bell Canada &amp; Vodacom Unique Identifier beacons"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2014-01-19</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Checking+known+AT%26T%2C+Verizon%2C+Sprint%2C+Bell+Canada+%26+Vodacom+Unique+Identifier+beacons&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Flessonslearned.org%2Fsniff&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-25"><span class="mw-cite-backlink"><b><a href="#cite_ref-25"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web">Craig Timberg. <a rel="nofollow" class="external text" href="http://www.washingtonpost.com/business/technology/verizon-atandt-tracking-their-users-with-super-cookies/2014/11/03/7bbbf382-6395-11e4-bb14-4cfea1e742d5_story.html">"Verizon, AT&amp;T tracking their users with 'supercookies<span style="padding-right:0.2em;">'</span>"</a>. <a href="/wiki/The_Washington_Post" title="The Washington Post">The Washington Post</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2014-01-19</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.au=Craig+Timberg&amp;rft.aulast=Craig+Timberg&amp;rft.btitle=Verizon%2C+AT%26T+tracking+their+users+with+%27supercookies%27&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fwww.washingtonpost.com%2Fbusiness%2Ftechnology%2Fverizon-atandt-tracking-their-users-with-super-cookies%2F2014%2F11%2F03%2F7bbbf382-6395-11e4-bb14-4cfea1e742d5_story.html&amp;rft.pub=The+Washington+Post&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-26"><span class="mw-cite-backlink"><b><a href="#cite_ref-26"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="https://help.sap.com/saphelp_nw74/helpdata/en/b3/5c22518bc72214e10000000a44176d/content.htm">"SAP Cross-Site Request Forgery Protection"</a>. <a href="/wiki/SAP_SE" title="SAP SE">SAP SE</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2015-01-20</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=SAP+Cross-Site+Request+Forgery+Protection&amp;rft.genre=book&amp;rft_id=https%3A%2F%2Fhelp.sap.com%2Fsaphelp_nw74%2Fhelpdata%2Fen%2Fb3%2F5c22518bc72214e10000000a44176d%2Fcontent.htm&amp;rft.pub=SAP+SE&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-27"><span class="mw-cite-backlink"><b><a href="#cite_ref-27"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="https://docs.djangoproject.com/en/1.7/ref/contrib/csrf/">"Django Cross Site Request Forgery protection"</a>. <a href="/wiki/Django_(web_framework)" title="Django (web framework)">Django (web framework)</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2015-01-20</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Django+Cross+Site+Request+Forgery+protection&amp;rft.genre=book&amp;rft_id=https%3A%2F%2Fdocs.djangoproject.com%2Fen%2F1.7%2Fref%2Fcontrib%2Fcsrf%2F&amp;rft.pub=Django+%28web+framework%29&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-28"><span class="mw-cite-backlink"><b><a href="#cite_ref-28"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="https://docs.angularjs.org/api/ng/service/$http#cross-site-request-forgery-xsrf-protection">"Angular Cross Site Request Forgery (XSRF) Protection"</a>. <a href="/wiki/AngularJS" title="AngularJS">AngularJS</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2015-01-20</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Angular+Cross+Site+Request+Forgery+%28XSRF%29+Protection&amp;rft.genre=book&amp;rft_id=https%3A%2F%2Fdocs.angularjs.org%2Fapi%2Fng%2Fservice%2F%24http%23cross-site-request-forgery-xsrf-protection&amp;rft.pub=AngularJS&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-29"><span class="mw-cite-backlink"><b><a href="#cite_ref-29"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc5789#section-3.1">"RFC 5789"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2014-12-24</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=RFC+5789&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc5789%23section-3.1&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-30"><span class="mw-cite-backlink"><b><a href="#cite_ref-30"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc6266">"RFC 6266"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2015-03-13</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=RFC+6266&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc6266&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-31"><span class="mw-cite-backlink"><b><a href="#cite_ref-31"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external free" href="https://tools.ietf.org/html/rfc7231#section-3.1.3.2">https://tools.ietf.org/html/rfc7231#section-3.1.3.2</a></span></li>
<li id="cite_note-32"><span class="mw-cite-backlink"><b><a href="#cite_ref-32"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7231#appendix-B">"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2015-06-03</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hypertext+Transfer+Protocol+%28HTTP%2F1.1%29%3A+Semantics+and+Content&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7231%23appendix-B&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-google_canonical-33"><span class="mw-cite-backlink"><b><a href="#cite_ref-google_canonical_33-0"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://support.google.com/webmasters/bin/answer.py?hl=en&amp;answer=139394">Indicate the canonical version of a URL by responding with the Link rel="canonical" HTTP header</a> Retrieved: 2012-02-09</span></li>
<li id="cite_note-34"><span class="mw-cite-backlink"><b><a href="#cite_ref-34"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text">W3C <a rel="nofollow" class="external text" href="http://www.w3.org/P3P">P3P Work Suspended</a></span></li>
<li id="cite_note-35"><span class="mw-cite-backlink"><b><a href="#cite_ref-35"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://www.rfc-editor.org/rfc/rfc7469.txt">"Public Key Pinning Extension for HTTP"</a>. IETF<span class="reference-accessdate">. Retrieved <span class="nowrap">17 April</span> 2015</span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Public+Key+Pinning+Extension+for+HTTP&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc7469.txt&amp;rft.pub=IETF&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-36"><span class="mw-cite-backlink"><b><a href="#cite_ref-36"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7231#section-7.1.3">"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2014-07-24</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hypertext+Transfer+Protocol+%28HTTP%2F1.1%29%3A+Semantics+and+Content&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7231%23section-7.1.3&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-37"><span class="mw-cite-backlink"><b><a href="#cite_ref-37"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7230#section-3.1.2">"Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2014-07-24</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hypertext+Transfer+Protocol+%28HTTP%2F1.1%29%3A+Message+Syntax+and+Routing&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7230%23section-3.1.2&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-38"><span class="mw-cite-backlink"><b><a href="#cite_ref-38"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc7034">"HTTP Header Field X-Frame-Options"</a>. IETF. 2013<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-06-12</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=HTTP+Header+Field+X-Frame-Options&amp;rft.date=2013&amp;rft.genre=book&amp;rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7034&amp;rft.pub=IETF&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-39"><span class="mw-cite-backlink"><b><a href="#cite_ref-39"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://www.w3.org/TR/CSP11/#frame-ancestors-and-frame-options">"Content Security Policy Level 2"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2014-08-02</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Content+Security+Policy+Level+2&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fwww.w3.org%2FTR%2FCSP11%2F%23frame-ancestors-and-frame-options&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-40"><span class="mw-cite-backlink"><b><a href="#cite_ref-40"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web">Eric Lawrence (2008-07-02). <a rel="nofollow" class="external text" href="http://blogs.msdn.com/b/ie/archive/2008/07/02/ie8-security-part-iv-the-xss-filter.aspx">"IE8 Security Part IV: The XSS Filter"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2010-09-30</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.au=Eric+Lawrence&amp;rft.aulast=Eric+Lawrence&amp;rft.btitle=IE8+Security+Part+IV%3A+The+XSS+Filter&amp;rft.date=2008-07-02&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fblogs.msdn.com%2Fb%2Fie%2Farchive%2F2008%2F07%2F02%2Fie8-security-part-iv-the-xss-filter.aspx&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-41"><span class="mw-cite-backlink"><b><a href="#cite_ref-41"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://www.w3.org/TR/CSP/">"Content Security Policy"</a>. W3C. 2012<span class="reference-accessdate">. Retrieved 2013</span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Content+Security+Policy&amp;rft.date=2012&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fwww.w3.org%2FTR%2FCSP%2F&amp;rft.pub=W3C&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-42"><span class="mw-cite-backlink"><b><a href="#cite_ref-42"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web">Eric Lawrence (2008-09-03). <a rel="nofollow" class="external text" href="http://blogs.msdn.com/b/ie/archive/2008/09/02/ie8-security-part-vi-beta-2-update.aspx">"IE8 Security Part VI: Beta 2 Update"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2010-09-28</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.au=Eric+Lawrence&amp;rft.aulast=Eric+Lawrence&amp;rft.btitle=IE8+Security+Part+VI%3A+Beta+2+Update&amp;rft.date=2008-09-03&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fblogs.msdn.com%2Fb%2Fie%2Farchive%2F2008%2F09%2F02%2Fie8-security-part-vi-beta-2-update.aspx&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-43"><span class="mw-cite-backlink"><b><a href="#cite_ref-43"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://code.google.com/chrome/extensions/hosting.html">"Hosting - Google Chrome Extensions - Google Code"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2012-06-14</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hosting+-+Google+Chrome+Extensions+-+Google+Code&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fcode.google.com%2Fchrome%2Fextensions%2Fhosting.html&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-44"><span class="mw-cite-backlink"><b><a href="#cite_ref-44"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://stackoverflow.com/questions/1288338/why-does-asp-net-framework-add-the-x-powered-byasp-net-http-header-in-response">"Why does ASP.NET framework add the 'X-Powered-By:ASP.NET' HTTP Header in responses? - Stack Overflow"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2010-09-30</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Why+does+ASP.NET+framework+add+the+%27X-Powered-By%3AASP.NET%27+HTTP+Header+in+responses%3F+-+Stack+Overflow&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fstackoverflow.com%2Fquestions%2F1288338%2Fwhy-does-asp-net-framework-add-the-x-powered-byasp-net-http-header-in-response&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-45"><span class="mw-cite-backlink"><b><a href="#cite_ref-45"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://msdn.microsoft.com/en-us/library/ie/cc288325%28v=vs.85%29.aspx#SetMode">"Defining Document Compatibility: Specifying Document Compatibility Modes"</a>. 2011-04-01<span class="reference-accessdate">. Retrieved <span class="nowrap">2012-01-24</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Defining+Document+Compatibility%3A+Specifying+Document+Compatibility+Modes&amp;rft.date=2011-04-01&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Flibrary%2Fie%2Fcc288325%2528v%3Dvs.85%2529.aspx%23SetMode&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-46"><span class="mw-cite-backlink"><b><a href="#cite_ref-46"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Configuring_servers_for_Ogg_media#Serve_X-Content-Duration_headers">"Configuring servers for Ogg media"</a>. 2014-05-26<span class="reference-accessdate">. Retrieved <span class="nowrap">2015-01-03</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Configuring+servers+for+Ogg+media&amp;rft.date=2014-05-26&amp;rft.genre=book&amp;rft_id=https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FWeb%2FHTTP%2FConfiguring_servers_for_Ogg_media%23Serve_X-Content-Duration_headers&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-47"><span class="mw-cite-backlink"><b><a href="#cite_ref-47"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="http://tools.ietf.org/html/rfc7234#section-5.4">"Hypertext Transfer Protocol (HTTP/1.1): Caching"</a>. ietf.org<span class="reference-accessdate">. Retrieved <span class="nowrap">2014-07-24</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=Hypertext+Transfer+Protocol+%28HTTP%2F1.1%29%3A+Caching&amp;rft.genre=book&amp;rft_id=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7234%23section-5.4&amp;rft.pub=ietf.org&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
<li id="cite_note-Q234067-48"><span class="mw-cite-backlink"><b><a href="#cite_ref-Q234067_48-0"><span class="cite-accessibility-label">Jump up </span>^</a></b></span> <span class="reference-text"><span class="citation web"><a rel="nofollow" class="external text" href="https://support.microsoft.com/en-us/kb/234067/">"How to prevent caching in Internet Explorer"</a>. <a href="/wiki/Microsoft" title="Microsoft">Microsoft</a>. 2011-09-22<span class="reference-accessdate">. Retrieved <span class="nowrap">2015-04-15</span></span>.</span><span title="ctx_ver=Z39.88-2004&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AList+of+HTTP+header+fields&amp;rft.btitle=How+to+prevent+caching+in+Internet+Explorer&amp;rft.date=2011-09-22&amp;rft.genre=book&amp;rft_id=https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fkb%2F234067%2F&amp;rft.pub=Microsoft&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook" class="Z3988"><span style="display:none;">&nbsp;</span></span></span></li>
</ol>
</div>
<h2><span class="mw-headline" id="External_links">External links</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=List_of_HTTP_header_fields&amp;action=edit&amp;section=13" title="Edit section: External links">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<ul>
<li><a rel="nofollow" class="external text" href="http://www.iana.org/assignments/message-headers/message-headers.xml#perm-headers%7CMessage">Headers: Permanent Message Header Field Names</a></li>
<li><a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc7230">RFC 7230</a>: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</li>
<li><a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc7231">RFC 7231</a>: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</li>
<li><a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc7232">RFC 7232</a>: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</li>
<li><a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc7233">RFC 7233</a>: Hypertext Transfer Protocol (HTTP/1.1): Range Requests</li>
<li><a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc7234">RFC 7234</a>: Hypertext Transfer Protocol (HTTP/1.1): Caching</li>
<li><a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc7235">RFC 7235</a>: Hypertext Transfer Protocol (HTTP/1.1): Authentication</li>
<li><a class="external mw-magiclink-rfc" rel="nofollow" href="//tools.ietf.org/html/rfc2965">RFC 2965</a>: IETF HTTP State Management Mechanism RFC</li>
<li><a rel="nofollow" class="external text" href="http://www.and.org/texts/server-http">HTTP/1.1 headers from a web server point of view</a></li>
<li><a rel="nofollow" class="external text" href="http://www.MyHTTP.info/">HTTP Request Header Viewer</a></li>
<li><a rel="nofollow" class="external text" href="http://viewdns.info/httpheaders/">HTTP Response Header Viewer</a> - Retrieves the HTTP response headers of any domain.</li>
<li><a rel="nofollow" class="external text" href="http://blogs.msdn.com/b/ieinternals/archive/2009/06/30/internet-explorer-custom-http-headers.aspx">Internet Explorer and Custom HTTP Headers - EricLaw's IEInternals - Site Home - MSDN Blogs</a></li>
<li><a rel="nofollow" class="external text" href="http://crwlr.net/">crwlr.net - HTTP Header index</a></li>
<li><a rel="nofollow" class="external text" href="http://www.privacyinfo.org/http-headers">HTTP Header with Privacyinfo</a> - Display your HTTP request and response headers</li>
</ul>
<!--
NewPP limit report
Parsed by mw1217
CPU time usage: 0.332 seconds
Real time usage: 0.365 seconds
Preprocessor visited node count: 1966/1000000
Preprocessor generated node count: 0/1500000
Post‐expand include size: 63456/2097152 bytes
Template argument size: 24/2097152 bytes
Highest expansion depth: 6/40
Expensive parser function count: 0/500
Lua time usage: 0.126/10.000 seconds
Lua memory usage: 2.74 MB/50 MB
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
100.00% 300.939 1 - -total
68.23% 205.336 1 - Template:Reflist
47.87% 144.046 43 - Template:Cite_web
12.47% 37.531 1 - Template:HTTP
11.22% 33.766 1 - Template:Sidebar
2.77% 8.326 1 - Template:Anchor
1.07% 3.231 1 - Template:Sic
0.81% 2.432 1 - Template:Column-width
-->
<!-- Saved in parser cache with key enwiki:pcache:idhash:13106156-0!*!0!!en!*!* and timestamp 20150810224756 and revision id 674390196
-->
<noscript>&lt;img src="//en.wikipedia.org/wiki/Special:CentralAutoLogin/start?type=1x1" alt="" title="" width="1" height="1" style="border: none; position: absolute;" /&gt;</noscript></div>
</div></body></html>
<title>Linke Relations</title>
<link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.0.1/css/bootstrap.min.css">    
<link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.0.1/css/bootstrap-theme.min.css"> 
<link rel="stylesheet" href="lib/pygments/syntax.css" type="text/css">
<link rel="stylesheet" href="css/typedef.css" type="text/css">   
<div class="container">
    <h1>Link Relations</h1>

1. Supporting: Saga Workflows

Link Relations for Long-Lived Compensating Transactions (Sagas)

@See:

rel="routing-slip"

Link to a resource representing a Routing Slip coordinating a Long-Lived Compensating Transaction

rel="compensatingtx"

Link to a resource representing information about a compensating transaction for each member transaction of a Long-Lived Compensating Transaction



2. Supporting: Event-Driven Workflows

Link Relations for an Even-Driven (E.g. Pubsubhubbub) Hypermedia Workflow

@See:

rel="ping"

When included in a resource representation of a hub, the "ping" link relation MAY identify a target resource that can be accessed to notify a hub about the occurrence of an event firing. Ping message SHOULD NOT contain any data except for the reference to where a hub should retrieve information about the pinged event from.

rel="sub"

When included in a resource representation of an event, the "sub" (subscription) link relation MAY identify a target resource that represents the ability to subscribe to the pub/sub event-type resource in the link context.

rel="unsub"

When included in a resource representation of an event, the "unsub" (subscription cancellation) link relation MAY identify a target resource that represents the ability to un-subscribe from the pub/sub event-type resource in the link context.

rel="event"

Resource representation of a subscribe-able events.

rel="events"

Link to a collection resource representing a list of subscribe-able events.


Contents of this page are intended for standardization and are released under CC0 1.0 Universal (CC0 1.0) Public Domain Dedication license by Irakli Nadareishvili. 2015.



</div><!-- /.container -->

<script src="//ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js"></script>
<script src="//netdna.bootstrapcdn.com/bootstrap/3.0.1/js/bootstrap.min.js"></script>

<!-- <script src="js/typedef.js"></script> -->
<script> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-54331678-1', 'auto'); ga('send', 'pageview'); </script>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment