initial commit

9 files changed, 1044 insertions, 0 deletions

diff --git a/files/it/web/http/headers/age/index.html b/files/it/web/http/headers/age/index.html
new file mode 100644
index 0000000000..5a4f1d20c3
--- /dev/null
+++ b/files/it/web/http/headers/age/index.html
@@ -0,0 +1,69 @@
+---
+title: Age
+slug: Web/HTTP/Headers/Age
+translation_of: Web/HTTP/Headers/Age
+---
+<div>{{HTTPSidebar}}</div>
+
+<p>L'header <code><strong>Age</strong></code> contiene il tempo in secondi di presenza dell'oggetto nella cache del proxy.</p>
+
+<p>L'header <code>Age</code> è solitamente prossimo allo zero. Se è <code>Age: 0</code>, è stato probabilmente da poco reperito dal server di origine; altrimenti viene calcolato come la differenza tra la data corrente del proxy e l' {{HTTPHeader("Date")}} header incluso nella risposta HTTP.</p>
+
+<table class="properties">
+ <tbody>
+  <tr>
+   <th scope="row">Header type</th>
+   <td>{{Glossary("Response header")}}</td>
+  </tr>
+  <tr>
+   <th scope="row">{{Glossary("Forbidden header name")}}</th>
+   <td>no</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Sintassi">Sintassi</h2>
+
+<pre class="syntaxbox">Age: &lt;delta-seconds&gt;
+</pre>
+
+<h2 id="Direttive">Direttive</h2>
+
+<dl>
+ <dt>&lt;delta-seconds&gt;</dt>
+ <dd>
+ <p>Un intero non negativo, che rappresenta il tempo in secondi di presenza dell'oggetto nella cache del proxy.</p>
+ </dd>
+</dl>
+
+<h2 id="Esempi">Esempi</h2>
+
+<pre>Age: 24</pre>
+
+<h2 id="Specifiche">Specifiche</h2>
+
+<table class="standard-table">
+ <tbody>
+  <tr>
+   <th scope="col">Specification</th>
+   <th scope="col">Title</th>
+  </tr>
+  <tr>
+   <td>{{RFC("7234", "Age", "5.1")}}</td>
+   <td>Hypertext Transfer Protocol (HTTP/1.1): Caching</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Compatibilità_Browser">Compatibilità Browser</h2>
+
+<p class="hidden">La tabella di compatibilità di questa pagina è generata dai dati strutturati. Se vuoi contribuire ai dati controlla <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> e inviaci una pull request.</p>
+
+<p>{{Compat("http.headers.Age")}}</p>
+
+<h2 id="Vedi_anche">Vedi anche</h2>
+
+<ul>
+ <li>{{HTTPHeader("Cache-Control")}}</li>
+ <li>{{HTTPHeader("Expires")}}</li>
+</ul>
diff --git a/files/it/web/http/headers/authorization/index.html b/files/it/web/http/headers/authorization/index.html
new file mode 100644
index 0000000000..0b732b40a2
--- /dev/null
+++ b/files/it/web/http/headers/authorization/index.html
@@ -0,0 +1,88 @@
+---
+title: Authorization
+slug: Web/HTTP/Headers/Authorization
+tags:
+  - Riferimenti
+translation_of: Web/HTTP/Headers/Authorization
+---
+<div>{{HTTPSidebar}}</div>
+
+<p>La richiesta header HTTP <strong><code>Authorization</code></strong> contiene le credenziali per autenticare un utente con il server, solitamente dopo che il server ha risposto con {{HTTPStatus("401")}} <code>Unauthorized</code> status e con un header {{HTTPHeader("WWW-Authenticate")}} .</p>
+
+<table class="properties">
+ <tbody>
+  <tr>
+   <th scope="row">Tipo Header</th>
+   <td>{{Glossary("richiesta header")}}</td>
+  </tr>
+  <tr>
+   <th scope="row">{{Glossary("Header name proibito")}}</th>
+   <td>no</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Sintassi">Sintassi</h2>
+
+<pre class="syntaxbox">Authorization: &lt;tipo&gt; &lt;credenziali&gt;</pre>
+
+<h2 id="Direttive">Direttive</h2>
+
+<dl>
+ <dt>&lt;tipo&gt;</dt>
+ <dd><a href="/en-US/docs/Web/HTTP/Authentication#Authentication_schemes">Tipo di autenticazione</a>. Un tipo comune è <a href="/en-US/docs/Web/HTTP/Authentication#Basic_authentication_scheme">"Basic"</a>. Altri tipi sono:
+ <ul>
+  <li><a href="http://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml">IANA registry of Authentication schemes</a></li>
+  <li><a href="http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html">Authentification for AWS servers (<code>AWS4-HMAC-SHA256</code>)</a></li>
+ </ul>
+ </dd>
+ <dt>&lt;credenziali&gt;</dt>
+ <dd>Se viene usato il tipo di autenticazione "Basic" le credenziali sono formate in questo modo:
+ <ul>
+  <li>Lo username e la password sono combinate con il simbolo dei due punti (<code>aladdin:opensesame</code>).</li>
+  <li>La stringa risultante è codificata in <a href="/en-US/docs/Web/API/WindowBase64/Base64_encoding_and_decoding">base64</a> (<code>YWxhZGRpbjpvcGVuc2VzYW1l</code>).</li>
+ </ul>
+
+ <div class="note">
+ <p><strong>Note</strong>: La codifica Base64 non significa che venga effettuato un hash o una cifratura! Questo metodo è sicuro tanto quanto mandare le credenziali in chiaro (base64 è un codifica reversibile). Preferibilmente usa la Basic Authentication assieme al protocollo HTTPS.</p>
+ </div>
+ </dd>
+</dl>
+
+<h2 id="Esempi">Esempi</h2>
+
+<pre>Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l
+</pre>
+
+<p>Guarda anche<a href="/en-US/docs/Web/HTTP/Authentication"> HTTP authentication</a> per esempi su come configurare i server Apache o nginx con password per proteggere i tuoi siti con l'autenticazione HTTP.</p>
+
+<h2 id="Specifiche">Specifiche</h2>
+
+<table class="standard-table">
+ <thead>
+  <tr>
+   <th scope="col">Specification</th>
+   <th scope="col">Title</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <td>{{RFC("7235", "Authorization", "4.2")}}</td>
+   <td>HTTP/1.1: Authentication</td>
+  </tr>
+  <tr>
+   <td>{{RFC("7617")}}</td>
+   <td>The 'Basic' HTTP Authentication Scheme</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Vedi_anche">Vedi anche</h2>
+
+<ul>
+ <li><a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a></li>
+ <li>{{HTTPHeader("WWW-Authenticate")}}</li>
+ <li>{{HTTPHeader("Proxy-Authorization")}}</li>
+ <li>{{HTTPHeader("Proxy-Authenticate")}}</li>
+ <li>{{HTTPStatus("401")}}, {{HTTPStatus("403")}}, {{HTTPStatus("407")}}</li>
+</ul>
diff --git a/files/it/web/http/headers/cookie/index.html b/files/it/web/http/headers/cookie/index.html
new file mode 100644
index 0000000000..b89fc207fd
--- /dev/null
+++ b/files/it/web/http/headers/cookie/index.html
@@ -0,0 +1,74 @@
+---
+title: Cookie
+slug: Web/HTTP/Headers/Cookie
+tags:
+  - Cookies
+  - Guida
+  - HTTP
+  - header
+  - richiesta
+translation_of: Web/HTTP/Headers/Cookie
+---
+<div>{{HTTPSidebar}}</div>
+
+<p><strong><code>Cookie</code></strong> è un'header di richiesta HTTP che contiene i <a href="/en-US/docs/Web/HTTP/Cookies"> cookie HTTP</a> memorizzati, precedentemente inviati dal server tramite l'header {{HTTPHeader("Set-Cookie")}}.</p>
+
+<p>L' header <code>Cookie</code> è opzionale e può essere omesso, per esempio, se le impostazioni di privacy del browser bloccano i cookie.</p>
+
+<table class="properties">
+ <tbody>
+  <tr>
+   <th scope="row">Tipo header</th>
+   <td>{{Glossary("Request header")}}</td>
+  </tr>
+  <tr>
+   <th scope="row">{{Glossary("Forbidden header name")}}</th>
+   <td>si</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Sintassi">Sintassi</h2>
+
+<pre class="syntaxbox">Cookie: &lt;cookie-list&gt;
+Cookie: name=value
+Cookie: name=value; name2=value2; name3=value3</pre>
+
+<dl>
+ <dt>&lt;cookie-list&gt;</dt>
+ <dd>Una lista di coppie chiave-valore nel formato <code>&lt;cookie-name&gt;=&lt;cookie-value&gt;</code>. Le coppie nella lista sono separate da un punto e virgola e uno spazio (<code>'; '</code>).</dd>
+</dl>
+
+<h2 id="Esempio">Esempio</h2>
+
+<pre>Cookie: PHPSESSID=298zf09hf012fh2; csrftoken=u32t4o3tb3gg43; _gat=1;</pre>
+
+<h2 id="Specifiche">Specifiche</h2>
+
+<table class="standard-table">
+ <thead>
+  <tr>
+   <th scope="col">Specifica</th>
+   <th scope="col">Titolo</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <td>{{RFC("6265", "Cookie", "5.4")}}</td>
+   <td>HTTP State Management Mechanism</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="compatibilità_dei_browser">compatibilità dei browser</h2>
+
+<p class="hidden">The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> and send us a pull request.</p>
+
+<p>{{Compat("http.headers.Cookie")}}</p>
+
+<h2 id="Vedi_anche">Vedi anche</h2>
+
+<ul>
+ <li>{{HTTPHeader("Set-Cookie")}}</li>
+ <li>{{domxref("Document.cookie")}}</li>
+</ul>
diff --git a/files/it/web/http/headers/host/index.html b/files/it/web/http/headers/host/index.html
new file mode 100644
index 0000000000..c5edcffb7b
--- /dev/null
+++ b/files/it/web/http/headers/host/index.html
@@ -0,0 +1,77 @@
+---
+title: Host
+slug: Web/HTTP/Headers/Host
+tags:
+  - HTTP
+  - Host
+  - Italiano
+  - Reference
+  - header
+translation_of: Web/HTTP/Headers/Host
+---
+<div>{{HTTPSidebar}}</div>
+
+<p>L'header di richiesta <code><strong>Host</strong></code> nei messaggi HTTP specifica il nome di dominio del server (per l'hosting virtuale) e (opzionalmente) il numero di porta TPC su cui il server è in ascolto.</p>
+
+<p>Se non viene specificata nessuna porta, viene utilizzata quella di default del servizio richiesto (ad esempio "80" per HTTP).</p>
+
+<p>L'header <code>Host</code> deve essere inviato in tutte le richieste HTTP/1.1. Un codice di stato (status code) {{HTTPStatus("400")}} (Bad Request) verrà inviato in risposta a qualsiasi richiesta HTTP/1.1 che non dispone di un campo header <code>Host</code> o ne contiene più di uno.</p>
+
+<table class="properties">
+ <tbody>
+  <tr>
+   <th scope="row">Tipo di header</th>
+   <td>{{Glossary("Header di richiesta")}}</td>
+  </tr>
+  <tr>
+   <th scope="row">{{Glossary("Nome header vietato")}}</th>
+   <td>Sì</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Sintassi">Sintassi</h2>
+
+<pre class="syntaxbox">Host: &lt;host&gt;:&lt;porta&gt;
+</pre>
+
+<h2 id="Direttive">Direttive</h2>
+
+<dl>
+ <dt>&lt;host&gt;</dt>
+ <dd>il nome di dominio del server (per l'hosting virtuale).</dd>
+ <dt>&lt;porta&gt; {{optional_inline}}</dt>
+ <dd>il numero di porta TCP su cui il server è in ascolto.</dd>
+</dl>
+
+<h2 id="Esempi">Esempi</h2>
+
+<pre>Host: developer.cdn.mozilla.net</pre>
+
+<h2 id="Specifiche">Specifiche</h2>
+
+<table class="standard-table">
+ <tbody>
+  <tr>
+   <th scope="col">Specifica</th>
+   <th scope="col">Titolo</th>
+  </tr>
+  <tr>
+   <td>{{RFC("7230", "Host", "5.4")}}</td>
+   <td>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Compatibilità_con_i_browser">Compatibilità con i browser</h2>
+
+<p class="hidden">La tabella di compatibilità in questa pagina è generata da dati strutturati. Se vuoi contribuire ai dati, per favore controlla <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> e inviaci una richiesta.</p>
+
+<p>{{Compat("http.headers.Host")}}</p>
+
+<h2 id="Vedi_anche">Vedi anche</h2>
+
+<ul>
+ <li>{{HTTPStatus("400")}}</li>
+ <li>{{HTMLElement("base")}}</li>
+</ul>
diff --git a/files/it/web/http/headers/index.html b/files/it/web/http/headers/index.html
new file mode 100644
index 0000000000..7d5b000ead
--- /dev/null
+++ b/files/it/web/http/headers/index.html
@@ -0,0 +1,368 @@
+---
+title: HTTP headers
+slug: Web/HTTP/Headers
+tags:
+  - HTTP
+  - Headers
+  - NeedsTranslation
+  - Networking
+  - Reference
+  - TopicStub
+translation_of: Web/HTTP/Headers
+---
+<div>{{HTTPSidebar}}</div>
+
+<p>HTTP headers allow the client and the server to pass additional information with the request or the response. A request header consists of its case-insensitive name followed by a colon '<code>:</code>', then by its value (without line breaks). Leading white space before the value is ignored.</p>
+
+<p>Custom proprietary headers can be added using the 'X-' prefix, but this convention was deprecated in June 2012, because of the inconveniences it caused when non-standard fields became standard in <a href="https://tools.ietf.org/html/rfc6648">RFC 6648</a>; others are listed in an <a class="external" href="http://www.iana.org/assignments/message-headers/perm-headers.html">IANA registry</a>, whose original content was defined in <a class="external" href="http://tools.ietf.org/html/rfc4229">RFC 4229</a>. IANA also maintains a <a class="external" href="http://www.iana.org/assignments/message-headers/prov-headers.html">registry of proposed new HTTP message headers</a>.</p>
+
+<p>Headers can be grouped according to their contexts:</p>
+
+<ul>
+	<li>{{Glossary("General header")}}: Headers applying to both requests and responses but with no relation to the data eventually transmitted in the body.</li>
+	<li>{{Glossary("Request header")}}: Headers containing more information about the resource to be fetched or about the client itself.</li>
+	<li>{{Glossary("Response header")}}: Headers with additional information about the response, like its location or about the server itself (name and version etc.).</li>
+	<li>{{Glossary("Entity header")}}: Headers containing more information about the body of the entity, like its content length or its MIME-type.</li>
+</ul>
+
+<p>Headers can also be grouped according to how proxies handle them:</p>
+
+<dl>
+	<dt><a id="e2e" name="e2e"></a>End-to-end headers</dt>
+	<dd>These headers must be transmitted to the final recipient of the message; that is, the server for a request or the client for a response. Intermediate proxies must retransmit end-to-end headers unmodified and caches must store them.</dd>
+	<dt><a id="hbh" name="hbh"></a>Hop-by-hop headers</dt>
+	<dd>These headers are meaningful only for a single transport-level connection and must not be retransmitted by proxies or cached. Such headers are: {{ httpheader("Connection") }}, {{ httpheader("Keep-Alive") }}, {{ httpheader("Proxy-Authenticate") }}, {{ httpheader("Proxy-Authorization") }}, {{ httpheader("TE") }}, {{ httpheader("Trailer") }}, {{ httpheader("Transfer-Encoding") }} and {{ httpheader("Upgrade") }}. Note that only hop-by-hop headers may be set using the {{ httpheader("Connection") }} general header.</dd>
+</dl>
+
+<p>The following list summarizes HTTP headers by their usage category. For an alphabetical list, see the navigation on the left side.</p>
+
+<h2 id="Authentication">Authentication</h2>
+
+<dl>
+	<dt>{{HTTPHeader("WWW-Authenticate")}}</dt>
+	<dd>Defines the authentication method that should be used to gain access to a resource.</dd>
+	<dt>{{HTTPHeader("Authorization")}}</dt>
+	<dd>Contains the credentials to authenticate a user agent with a server.</dd>
+	<dt>{{HTTPHeader("Proxy-Authenticate")}}</dt>
+	<dd>Defines the authentication method that should be used to gain access to a resource behind a Proxy server.</dd>
+	<dt>{{HTTPHeader("Proxy-Authorization")}}</dt>
+	<dd>Contains the credentials to authenticate a user agent with a proxy server.</dd>
+</dl>
+
+<h2 id="Caching">Caching</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Age")}}</dt>
+	<dd>The time in seconds the object has been in a proxy cache.</dd>
+	<dt>{{HTTPHeader("Cache-Control")}}</dt>
+	<dd>Specifies directives for caching mechanisms in both requests and responses.</dd>
+	<dt>{{HTTPHeader("Expires")}}</dt>
+	<dd>The date/time after which the response is considered stale.</dd>
+	<dt>{{HTTPHeader("Pragma")}}</dt>
+	<dd>Implementation-specific header that may have various effects anywhere along the request-response chain. Used for backwards compatibility with HTTP/1.0 caches where the <code>Cache-Control</code> header is not yet present.</dd>
+	<dt>{{HTTPHeader("Warning")}}</dt>
+	<dd>A general warning field containing information about possible problems.</dd>
+</dl>
+
+<h2 id="Client_hints">Client hints</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Accept-CH")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Content-DPR")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("DPR")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Downlink")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Save-Data")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Viewport-Width")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Width")}}</dt>
+	<dd>...</dd>
+</dl>
+
+<dl>
+	<dt>
+	<h2 id="Conditionals">Conditionals</h2>
+	</dt>
+	<dt>{{HTTPHeader("Last-Modified")}}</dt>
+	<dd>It is a validator, the last modification date of the resource, used to compare several versions of the same resource. It is less accurate than {{HTTPHeader("ETag")}}, but easier to calculate in some environments. Conditional requests using {{HTTPHeader("If-Modified-Since")}} and {{HTTPHeader("If-Unmodified-Since")}} use this value to change the behavior of the request.</dd>
+	<dt>{{HTTPHeader("ETag")}}</dt>
+	<dd>It is a validator, a unique string identifying the version of the resource. Conditional requests using {{HTTPHeader("If-Match")}} and {{HTTPHeader("If-None-Match")}} use this value to change the behavior of the request.</dd>
+	<dt>{{HTTPHeader("If-Match")}}</dt>
+	<dd>Makes the request conditional and applies the method only if the stored resource matches one of the given ETags.</dd>
+	<dt>{{HTTPHeader("If-None-Match")}}</dt>
+	<dd>Makes the request conditional and applies the method only if the stored resource doesn't match any of the given ETags. This is used to update caches (for safe requests), or to prevent to upload a new resource when one is already existing.</dd>
+	<dt>{{HTTPHeader("If-Modified-Since")}}</dt>
+	<dd>Makes the request conditional and expects the entity to be transmitted only if it has been modified after the given date. This is used to transmit data only when the cache is out of date.</dd>
+	<dt>{{HTTPHeader("If-Unmodified-Since")}}</dt>
+	<dd>Makes the request conditional and expects the entity to be transmitted only if it has not been modified after the given date. This is used to ensure the coherence of a new fragment of a specific range with previous ones, or to implement an optimistic concurrency control system when modifying existing documents.</dd>
+</dl>
+
+<h2 id="Connection_management">Connection management</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Connection")}}</dt>
+	<dd>Controls whether the network connection stays open after the current transaction finishes.</dd>
+	<dt>{{HTTPHeader("Keep-Alive")}}</dt>
+	<dd>Controls how long a persistent connection should stay open.</dd>
+</dl>
+
+<h2 id="Content_negotiation">Content negotiation</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Accept")}}</dt>
+	<dd>Informs the server about the types of data that can be sent back. It is MIME-type.</dd>
+	<dt>{{HTTPHeader("Accept-Charset")}}</dt>
+	<dd>Informs the server about which character set the client is able to understand.</dd>
+	<dt>{{HTTPHeader("Accept-Encoding")}}</dt>
+	<dd>Informs the server about the encoding algorithm, usually a compression algorithm, that can be used on the resource sent back.</dd>
+	<dt>{{HTTPHeader("Accept-Language")}}</dt>
+	<dd>Informs the server about the language the server is expected to send back. This is a hint and is not necessarily under the full control of the user: the server should always pay attention not to override an explicit user choice (like selecting a language in a drop down list).</dd>
+</dl>
+
+<dl>
+</dl>
+
+<h2 id="Controls">Controls</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Expect")}}</dt>
+	<dd>Indicates expectations that need to be fulfilled by the server in order to properly handle the request.</dd>
+	<dt>{{HTTPHeader("Max-Forwards")}}</dt>
+	<dd>...</dd>
+</dl>
+
+<h2 id="Cookies">Cookies</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Cookie")}}</dt>
+	<dd>Contains stored <a href="/en-US/docs/Web/HTTP/Cookies">HTTP cookies</a> previously sent by the server with the {{HTTPHeader("Set-Cookie")}} header.</dd>
+	<dt>{{HTTPHeader("Set-Cookie")}}</dt>
+	<dd>Send cookies from the server to the user agent.</dd>
+	<dt>{{HTTPHeader("Cookie2")}} {{obsolete_inline}}</dt>
+	<dd>Used to contain an HTTP cookie, previously sent by the server with the {{HTTPHeader("Set-Cookie2")}} header, but has been obsoleted by the specification. Use {{HTTPHeader("Cookie")}} instead.</dd>
+	<dt>{{HTTPHeader("Set-Cookie2")}} {{obsolete_inline}}</dt>
+	<dd>Used to send cookies from the server to the user agent, but has been obsoleted by the specification. Use {{HTTPHeader("Set-Cookie")}} instead.</dd>
+	<dt>
+	<h2 id="CORS">CORS</h2>
+	</dt>
+	<dt>{{HTTPHeader("Access-Control-Allow-Origin")}}</dt>
+	<dd>Indicates whether the response can be shared.</dd>
+	<dt>{{HTTPHeader("Access-Control-Allow-Credentials")}}</dt>
+	<dd>Indicates whether the response to the request can be exposed when the credentials flag is true.</dd>
+	<dt>{{HTTPHeader("Access-Control-Allow-Headers")}}</dt>
+	<dd>Used in response to a preflight request to indicate which HTTP headers can be used when making the actual request.</dd>
+	<dt>{{HTTPHeader("Access-Control-Allow-Methods")}}</dt>
+	<dd>Specifies the method or methods allowed when accessing the resource in response to a preflight request.</dd>
+	<dt>{{HTTPHeader("Access-Control-Expose-Headers")}}</dt>
+	<dd>Indicates which headers can be exposed as part of the response by listing their names.</dd>
+	<dt>{{HTTPHeader("Access-Control-Max-Age")}}</dt>
+	<dd>Indicates how long the results of a preflight request can be cached.</dd>
+	<dt>{{HTTPHeader("Access-Control-Request-Headers")}}</dt>
+	<dd>Used when issuing a preflight request to let the server know which HTTP headers will be used when the actual request is made.</dd>
+	<dt>{{HTTPHeader("Access-Control-Request-Method")}}</dt>
+	<dd>Used when issuing a preflight request to let the server know which <a href="/en-US/docs/Web/HTTP/Methods">HTTP method</a> will be used when the actual request is made.</dd>
+	<dt>{{HTTPHeader("Origin")}}</dt>
+	<dd>Indicates where a fetch originates from.</dd>
+</dl>
+
+<h2 id="Do_Not_Track">Do Not Track</h2>
+
+<dl>
+	<dt>{{HTTPHeader("DNT")}}</dt>
+	<dd>Used for expressing the user's tracking preference.</dd>
+	<dt>{{HTTPHeader("Tk")}}</dt>
+	<dd>Indicates the tracking status that applied to the corresponding request.</dd>
+</dl>
+
+<h2 id="Downloads">Downloads</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Content-Disposition")}}</dt>
+	<dd>Is a response header if the resource transmitted should be displayed inline (default behavior when the header is not present), or it should be handled like a download and the browser should present a 'Save As' window.</dd>
+</dl>
+
+<h2 id="Message_body_information">Message body information</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Content-Length")}}</dt>
+	<dd>indicates the size of the entity-body, in decimal number of octets, sent to the recipient.</dd>
+	<dt>{{HTTPHeader("Content-Type")}}</dt>
+	<dd>Indicates the media type of the resource.</dd>
+	<dt>{{HTTPHeader("Content-Encoding")}}</dt>
+	<dd>Used to specify the compression algorithm.</dd>
+	<dt>{{HTTPHeader("Content-Language")}}</dt>
+	<dd>Describes the language(s) intended for the audience, so that it allows a user to differentiate according to the users' own preferred language.</dd>
+	<dt>{{HTTPHeader("Content-Location")}}</dt>
+	<dd>Indicates an alternate location for the returned data.</dd>
+	<dt>
+	<h2 id="Proxies">Proxies</h2>
+	</dt>
+</dl>
+
+<dl>
+	<dt>{{HTTPHeader("Forwarded")}}</dt>
+	<dd>Contains information from the client-facing side of proxy servers that is altered or lost when a proxy is involved in the path of the request.</dd>
+	<dt>{{HTTPHeader("X-Forwarded-For")}} {{non-standard_inline}}</dt>
+	<dd>Identifies the originating IP addresses of a client connecting to a web server through an HTTP proxy or a load balancer.</dd>
+	<dt>{{HTTPHeader("X-Forwarded-Host")}} {{non-standard_inline}}</dt>
+	<dd>Identifies the original host requested that a client used to connect to your proxy or load balancer.</dd>
+	<dt>{{HTTPHeader("X-Forwarded-Proto")}} {{non-standard_inline}}</dt>
+	<dd>identifies the protocol (HTTP or HTTPS) that a client used to connect to your proxy or load balancer.</dd>
+	<dt>{{HTTPHeader("Via")}}</dt>
+	<dd>Added by proxies, both forward and reverse proxies, and can appear in the request headers and the response headers.</dd>
+</dl>
+
+<h2 id="Redirects">Redirects</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Location")}}</dt>
+	<dd>Indicates the URL to redirect a page to.</dd>
+</dl>
+
+<h2 id="Request_context">Request context</h2>
+
+<dl>
+	<dt>{{HTTPHeader("From")}}</dt>
+	<dd>Contains an Internet email address for a human user who controls the requesting user agent.</dd>
+	<dt>{{HTTPHeader("Host")}}</dt>
+	<dd>Specifies the domain name of the server (for virtual hosting), and (optionally) the TCP port number on which the server is listening.</dd>
+	<dt>{{HTTPHeader("Referer")}}</dt>
+	<dd>The address of the previous web page from which a link to the currently requested page was followed.</dd>
+	<dt>{{HTTPHeader("Referrer-Policy")}}</dt>
+	<dd>Governs which referrer information sent in the {{HTTPHeader("Referer")}} header should be included with requests made.</dd>
+	<dt>{{HTTPHeader("User-Agent")}}</dt>
+	<dd>Contains a characteristic string that allows the network protocol peers to identify the application type, operating system, software vendor or software version of the requesting software user agent. See also the <a href="/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox">Firefox user agent string reference</a>.</dd>
+</dl>
+
+<h2 id="Response_context">Response context</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Allow")}}</dt>
+	<dd>Lists the set of HTTP request methods support by a resource.</dd>
+	<dt>{{HTTPHeader("Server")}}</dt>
+	<dd>Contains information about the software used by the origin server to handle the request.</dd>
+</dl>
+
+<h2 id="Range_requests">Range requests</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Accept-Ranges")}}</dt>
+	<dd>Indicates if the server supports range requests and if so, in which unit the range can be expressed.</dd>
+	<dt>{{HTTPHeader("Range")}}</dt>
+	<dd>Indicates the part of a document that the server should return.</dd>
+	<dt>{{HTTPHeader("If-Range")}}</dt>
+	<dd>Creates a conditional range request that is only fulfilled if the given etag or date matches the remote resource. Used to prevent downloading two ranges from incompatible version of the resource.</dd>
+	<dt>{{HTTPHeader("Content-Range")}}</dt>
+	<dd>Indicates where in a full body message a partial message belongs.</dd>
+</dl>
+
+<h2 id="Security">Security</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Content-Security-Policy")}} ({{Glossary("CSP")}})</dt>
+	<dd>Controls resources the user agent is allowed to load for a given page.</dd>
+	<dt>{{HTTPHeader("Content-Security-Policy-Report-Only")}}</dt>
+	<dd>Allows web developers to experiment with policies by monitoring (but not enforcing) their effects. These violation reports consist of {{Glossary("JSON")}} documents sent via an HTTP <code>POST</code> request to the specified URI.</dd>
+	<dt>{{HTTPHeader("Public-Key-Pins")}} ({{Glossary("HPKP")}})</dt>
+	<dd>Associates a specific cryptographic public key with a certain web server to decrease the risk of {{Glossary("MITM")}} attacks with forged certificates.</dd>
+	<dt>{{HTTPHeader("Public-Key-Pins-Report-Only")}}</dt>
+	<dd>Sends reports to the report-uri specified in the header and does still allow clients to connect to the server even if the pinning is violated.</dd>
+</dl>
+
+<dl>
+	<dt>{{HTTPHeader("Strict-Transport-Security")}} ({{Glossary("HSTS")}})</dt>
+	<dd>Force communication using HTTPS instead of HTTP.</dd>
+	<dt>{{HTTPHeader("Upgrade-Insecure-Requests")}}</dt>
+	<dd>Sends a signal to the server expressing the client’s preference for an encrypted and authenticated response, and that it can successfully handle the {{CSP("upgrade-insecure-requests")}} directive.</dd>
+</dl>
+
+<dl>
+	<dt>{{HTTPHeader("X-Content-Type-Options")}}</dt>
+	<dd>Disables MIME sniffing and forces browser to use the type given in {{HTTPHeader("Content-Type")}}.</dd>
+</dl>
+
+<dl>
+	<dt>{{HTTPHeader("X-Frame-Options")}} (XFO)</dt>
+	<dd>Indicates whether a browser should be allowed to render a page in a {{HTMLElement("frame")}}, {{HTMLElement("iframe")}} or {{HTMLElement("object")}}</dd>
+	<dt>{{HTTPHeader("X-XSS-Protection")}}</dt>
+	<dd>Enables cross-site scripting filtering.</dd>
+</dl>
+
+<h2 id="Server-sent_events">Server-sent events</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Ping-From")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Ping-To")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Last-Event-ID")}}</dt>
+	<dd>...</dd>
+</dl>
+
+<h2 id="Transfer_coding">Transfer coding</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Transfer-Encoding")}}</dt>
+	<dd>Specifies the the form of encoding used to safely transfer the entity to the user.</dd>
+	<dt>{{HTTPHeader("TE")}}</dt>
+	<dd>Specifies the transfer encodings the user agent is willing to accept.</dd>
+	<dt>{{HTTPHeader("Trailer")}}</dt>
+	<dd>Allows the sender to include additional fields at the end of chunked message.</dd>
+</dl>
+
+<h2 id="WebSockets">WebSockets</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Sec-WebSocket-Key")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Sec-WebSocket-Extensions")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Sec-WebSocket-Accept")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Sec-WebSocket-Protocol")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Sec-WebSocket-Version")}}</dt>
+	<dd>...</dd>
+</dl>
+
+<h2 id="Other">Other</h2>
+
+<dl>
+	<dt>{{HTTPHeader("Date")}}</dt>
+	<dd>Contains the date and time at which the message was originated.</dd>
+	<dt>{{HTTPHeader("Large-Allocation")}}</dt>
+	<dd>Tells the browser that the page being loaded is going to want to perform a large allocation.</dd>
+	<dt>{{HTTPHeader("Link")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("Retry-After")}}</dt>
+	<dd>Indicates how long the user agent should wait before making a follow-up request.</dd>
+	<dt>{{HTTPHeader("SourceMap")}}</dt>
+	<dd>Links generated code to a <a href="/en-US/docs/Tools/Debugger/How_to/Use_a_source_map">source map</a>.</dd>
+	<dt>{{HTTPHeader("Upgrade")}}</dt>
+	<dd>The relevant RFC document for the <a href="https://tools.ietf.org/html/rfc7230#section-6.7">Upgrade header field is RFC 7230, section 6.7</a>.  The standard establishes rules for upgrading or changing to a different protocol on the current client, server, transport protocol connection.  For example, this header standard allows a client to change from HTTP 1.1 to HTTP 2.0, assuming the server decides to acknowledge and implement the Upgrade header field.  Niether party is required to accept the terms specified in the Upgrade header field.  It can be used in both client and server headers.  If the Upgrade header field is specified, then the sender MUST also send the Connection header field with the upgrade option specified.  For details on the Connection header field <a href="https://tools.ietf.org/html/rfc7230#section-6.1">please see section 6.1 of the aforementioned RFC</a>.</dd>
+	<dt>{{HTTPHeader("Vary")}}</dt>
+	<dd>Determines how to match future request headers to decide whether a cached response can be used rather than requesting a fresh one from the origin server.</dd>
+	<dt>{{HTTPHeader("X-DNS-Prefetch-Control")}}</dt>
+	<dd>Controls DNS prefetching, a feature by which browsers proactively perform domain name resolution on both links that the user may choose to follow as well as URLs for items referenced by the document, including images, CSS, JavaScript, and so forth.</dd>
+	<dt>{{HTTPHeader("X-Firefox-Spdy")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("X-Requested-With")}}</dt>
+	<dd>...</dd>
+	<dt>{{HTTPHeader("X-UA-Compatible")}}</dt>
+	<dd>...</dd>
+</dl>
+
+<h2 id="Contributing">Contributing</h2>
+
+<p>You can help by <a href="/en-US/docs/MDN/Contribute/Howto/Document_an_HTTP_header">writing new entries</a> or improving the existing ones.</p>
+
+<h2 id="See_also">See also</h2>
+
+<ul>
+	<li><a href="https://en.wikipedia.org/wiki/List_of_HTTP_header_fields">Wikipedia page on List of HTTP headers</a></li>
+	<li><a href="https://www.iana.org/assignments/message-headers/perm-headers.html">IANA registry</a></li>
+</ul>
diff --git a/files/it/web/http/headers/server/index.html b/files/it/web/http/headers/server/index.html
new file mode 100644
index 0000000000..46e9030558
--- /dev/null
+++ b/files/it/web/http/headers/server/index.html
@@ -0,0 +1,70 @@
+---
+title: Server
+slug: Web/HTTP/Headers/Server
+tags:
+  - HTTP
+  - Riferimento
+  - header
+translation_of: Web/HTTP/Headers/Server
+---
+<div>{{HTTPSidebar}}</div>
+
+<div>L'header <code><strong>Server</strong></code> contiene informazioni sul software utilizzato dal server di origine per gestire la richiesta.</div>
+
+<p>Valori di Server troppo lunghi e dettagliati dovrebbero essere evitati, poiché potenzialmente rivelano dettagli interni di implementazione che potrebbero rendere (leggermente) più facile per degli hacker trovare e sfruttare falle di sicurezza note.</p>
+
+<table class="properties">
+ <tbody>
+  <tr>
+   <th scope="row">Tipo header</th>
+   <td>{{Glossary("Header di risposta")}}</td>
+  </tr>
+  <tr>
+   <th scope="row">{{Glossary("Forbidden header name")}}</th>
+   <td>no</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Sintassi">Sintassi</h2>
+
+<pre class="syntaxbox">Server: &lt;prodotto&gt;
+</pre>
+
+<h2 id="Direttive">Direttive</h2>
+
+<dl>
+ <dt>&lt;prodotto&gt;</dt>
+ <dd>Il nome del software o (sotto)prodotto che gestisce le richieste.</dd>
+</dl>
+
+<h2 id="Esempi">Esempi</h2>
+
+<pre>Server: Apache/2.4.1 (Unix)</pre>
+
+<h2 id="Specifiche">Specifiche</h2>
+
+<table class="standard-table">
+ <tbody>
+  <tr>
+   <th scope="col">Specifica</th>
+   <th scope="col">Titolo</th>
+  </tr>
+  <tr>
+   <td>{{RFC("7231", "Server", "7.4.2")}}</td>
+   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Compatibilità_browser">Compatibilità browser</h2>
+
+<p class="hidden">The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> and send us a pull request.</p>
+
+<p>{{Compat("http.headers.Server")}}</p>
+
+<h2 id="Vedi_anche">Vedi anche</h2>
+
+<ul>
+ <li>{{HTTPHeader("Allow")}}</li>
+</ul>
diff --git a/files/it/web/http/headers/strict-transport-security/index.html b/files/it/web/http/headers/strict-transport-security/index.html
new file mode 100644
index 0000000000..cad174395e
--- /dev/null
+++ b/files/it/web/http/headers/strict-transport-security/index.html
@@ -0,0 +1,118 @@
+---
+title: Strict-Transport-Security
+slug: Web/HTTP/Headers/Strict-Transport-Security
+tags:
+  - HSTS
+  - HTTP
+  - HTTPS
+  - Sicurezza
+  - header
+translation_of: Web/HTTP/Headers/Strict-Transport-Security
+---
+<div>{{HTTPSidebar}}</div>
+
+<p>L'header di risposta<strong> </strong>HTTP <strong><code>Strict-Transport-Security</code></strong>  (spesso abbreviato come {{Glossary("HSTS")}})  è una funzionalità di sicurezza che consente ad un sito web di comunicare ai browser che tutte le richieste devono essere effettuate usando HTTPS invece di HTTP.</p>
+
+<p>informare i browser a comunicare esclusivamente usando HTTPS, invece che HTTP.</p>
+
+<table class="properties">
+ <tbody>
+  <tr>
+   <th scope="row">Header type</th>
+   <td>{{Glossary("Response header")}}</td>
+  </tr>
+  <tr>
+   <th scope="row">{{Glossary("Forbidden header name")}}</th>
+   <td>no</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Sintassi">Sintassi</h2>
+
+<pre class="syntaxbox">Strict-Transport-Security: max-age=&lt;expire-time&gt;
+Strict-Transport-Security: max-age=&lt;expire-time&gt;; includeSubDomains
+Strict-Transport-Security: max-age=&lt;expire-time&gt;; preload
+</pre>
+
+<h2 id="Direttive">Direttive</h2>
+
+<dl>
+ <dt><code>max-age=&lt;expire-time&gt;</code></dt>
+ <dd>Il tempo, in secondi, per il quale il browser deve ricordare che il sito è accessibile solamente utilizzando HTTPS.</dd>
+ <dt><code>includeSubDomains</code> {{optional_inline}}</dt>
+ <dd>Se questo parametro opzionale è specificato, la regola si applica anche a tutti i sotto domini.</dd>
+ <dt><code>preload</code> {{optional_inline}}</dt>
+ <dd>Consulta {{anch("Preloading Strict Transport Security")}} per i dettagli. Non è parte delle specifiche.</dd>
+</dl>
+
+<h2 id="Descrizione">Descrizione</h2>
+
+<p>Se un sito web accetta connessioni attraverso HTTP e reindirizza su HTTPS, l'utente potrebbe inizializzare la connessione non cifrata, prima di essere rediretto, ad esempio se digitasse http://www.foo.com/ o solamente foo.com.</p>
+
+<p>Questo sistema apre ad un potenziale attacco di tipo man-in-the-middle, dove la redirezione può essere sfruttata per indirizzare l'attaccante ad un sito malevolo invece che alla versione sicura della pagina originale.</p>
+
+<p>L'header HTTP Strict Transport Security consente ad un sito web di informare il browser che non dovrebbe mai caricare il sito utilizzando HTTP e dovrebbe automaticamente convertire i tentativi di accesso al sito tramite HTTP, in HTTPS.</p>
+
+<div class="note"><strong>Nota:</strong> L'header <code>Strict-Transport-Security</code> è ignorato dal browser quanto il sito viene caricato tramite HTTP; questo perchè un attaccante potrebbe intercettare la connessione HTTP e iniettare o modificare l'header. Quando il sito è caricato tramite HTTPS senza errori di certificato, il browser saprà che il sito è disponibile tramite HTTPS e rispetterà l'header <code>Strict-Transport-Security</code>.</div>
+
+<h3 id="Uno_scenario_desempio">Uno scenario d'esempio</h3>
+
+<p>Effettui l'accesso ad una rete WiFi aperta all'aereoporto e inizi a navigare nel web, visitando il sito della tua banca per controllare il tuo saldo e per pagare un paio di bollette. Sfortunatamente, l'access point che stai utilizzando è in realtà il computer di un hacker che sta intercettando le tue richieste originali in HTTP e reindirizzandoti ad un sito web clone della tua banca invece che al sito originale. Ora tutti i tuoi dati privati sono esposti all'hacker.</p>
+
+<p>Strict Transport Security risolve questo problema; a patto che tu abbia già visitato in precedenza il sito della tua banca utilizzando HTTPS e a patto che il sito web utilizzi Strict Transport Security, il tuo browser utilizzerà automaticamente HTTPS, che impedisce agli hacker di effettuare un attacco di tipo man-in-the-middle.</p>
+
+<h3 id="Come_viene_gestito_dal_browser">Come viene gestito dal browser</h3>
+
+<p>La prima volta che il tuo sito web viene contattato utilizzando HTTPS e restituisce l'header <code>Strict-Transport-Security</code>, il browser registra questa informazione, in modo che tutti i futuri tentativi di caricare il sito attraverso HTTP verranno modificati utilizzando HTTPS.</p>
+
+<p>Quando il tempo di validità specificato dall'header Strict-Transport-Security scade, il seguente tentativo di caricare il sito web via HTTP procederà normalmente invece che utilizzare automaticamente HTTPS.</p>
+
+<p>Ogni qual volta l'header<em> Strict-Transport-Security</em> viene inviato al browser, il tempo di validità sarà aggiornato per quel sito, quindi i siti possono aggioranre questa informazione per prevenire la scadenza della validità. Nel caso in cui fosse necessario disabilitare Strict Transport Security, impostare l'attributo max-age a 0 (su una connession HTTPS) porterà immediatamente alla scadenza dell'header stesso, consentendo l'accesso via HTTP.</p>
+
+<h2 id="Precaricamento_di_Strict_Transport_Security">Precaricamento di Strict Transport Security</h2>
+
+<p>Google mantiene un <a href="https://hstspreload.appspot.com/">servizio di precaricamento per HSTS</a>. Seguendo le linee guida e inviando con successo il tuo dominio, i browser non si connetteranno mai allo stesso utilizzando connessioni insicure. Sebbene il servizio sia ospitato da Google, tutti i browser hanno dichiarato l'intento di iniziare ad utilizzare (o effettivamente utilizzare) la lista di precaricamento.</p>
+
+<ul>
+ <li>Informazioni riguardanti la lista di precaricamento per HSTS in Chrome: <a href="https://www.chromium.org/hsts">https://www.chromium.org/hsts</a></li>
+ <li>Informazioni riguardanti la lista di precaricamento per HSTS in Firefox: <a href="https://dxr.mozilla.org/comm-central/source/mozilla/security/manager/ssl/nsSTSPreloadList.inc">nsSTSPreloadList.inc</a></li>
+</ul>
+
+<h2 id="Esempio">Esempio</h2>
+
+<p>Tutti i presenti e futuri sottodomini saranno contattati in HTTPS per un <em>max-age</em> di 1 anno. Questo impedisce l'accesso alle pagine o ai sottodomini che possono essere forniti solo tramite HTTP.</p>
+
+<pre>Strict-Transport-Security: max-age=31536000; includeSubDomains</pre>
+
+<h2 id="Specifiche">Specifiche</h2>
+
+<table class="standard-table">
+ <tbody>
+  <tr>
+   <th scope="col">Specifica</th>
+   <th scope="col">Stato</th>
+   <th scope="col">Commento</th>
+  </tr>
+  <tr>
+   <td>{{SpecName('HSTS')}}</td>
+   <td>{{Spec2('HSTS')}}</td>
+   <td>Initial definition</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Compatibilità_browser">Compatibilità browser</h2>
+
+<p class="hidden">La tabella di compatibilità in questa pagina è generata da dati strutturati. Se volessi contribuire, controlla <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> e inviaci una pull-request.</p>
+
+<p>{{Compat("http.headers.Strict-Transport-Security")}}</p>
+
+<h2 id="Vedi_anche">Vedi anche</h2>
+
+<ul>
+ <li>Blog post: <a class="external" href="http://blog.sidstamm.com/2010/08/http-strict-transport-security-has.html">HTTP Strict Transport Security has landed!</a></li>
+ <li>Blog post: <a class="external" href="http://hacks.mozilla.org/2010/08/firefox-4-http-strict-transport-security-force-https/">HTTP Strict Transport Security (force HTTPS)</a></li>
+ <li>OWASP Article: <a href="https://www.owasp.org/index.php/HTTP_Strict_Transport_Security">HTTP Strict Transport Security</a></li>
+ <li>Wikipedia: <a href="http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security">HTTP Strict Transport Security</a></li>
+</ul>
diff --git a/files/it/web/http/headers/x-content-type-options/index.html b/files/it/web/http/headers/x-content-type-options/index.html
new file mode 100644
index 0000000000..ac06e93904
--- /dev/null
+++ b/files/it/web/http/headers/x-content-type-options/index.html
@@ -0,0 +1,90 @@
+---
+title: X-Content-Type-Options
+slug: Web/HTTP/Headers/X-Content-Type-Options
+tags:
+  - HTTP
+  - HTTP Header
+  - Reference
+  - ResponseHeader
+translation_of: Web/HTTP/Headers/X-Content-Type-Options
+---
+<p>L'header <code><strong>X-Content-Type-Options</strong></code> delle risposte HTTP è usato per indicare che il <a href="/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types">tipo MIME</a> descritto dagli header di tipo {{HTTPHeader("Content-Type")}} dovrebbe venire rispettato senza effettuare modifiche. Questo consente di al client di non effettuare lo <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#MIME_sniffing">sniffing del tipo MIME</a>, o, in altre parole, è un modo con cui i webmaster comunicano che "sapevano cosa stessero facendo".</p>
+
+<p>Questo header è stato introdotto da Microsoft con IE8 per consentire ai webmaster di impedire lo sniffing del tipo MIME, che avveniva comunemente, ma che poteva comportare la conversione di un tipo MIME non eseguibile in uno eseguibile. Da allora altri browser hanno iniziato a supportarlo, nonostante i loro algoritmi di sniffing siano meno aggressivi rispetto al passato.</p>
+
+<p>I tester della sicurezza dei siti solitamente si aspettano di trovare questo header.</p>
+
+<p class="blockIndicator note">Nota: <code>X-Content-Type-Options</code> causa il <a href="https://fetch.spec.whatwg.org/#should-response-to-request-be-blocked-due-to-nosniff?">blocco di una richiesta se il suo valore è <code>nosniff</code></a> solo per <a href="https://fetch.spec.whatwg.org/#concept-request-destination">richieste con destinazione</a> di tipo "<code>script</code>" o "<code>style</code>". Tale header causa anche It also <a href="https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md#what-types-of-content-are-protected-by-corb">l'attivazione del Cross-Origin Read Blocking (CORB)</a> per file di tipo HTML, TXT, JSON e XML ( i file SVG <code>image/svg+xml</code> sono esclusi).</p>
+
+<table class="properties">
+ <tbody>
+  <tr>
+   <th scope="row">Tipo Header</th>
+   <td>{{Glossary("Response header")}}</td>
+  </tr>
+  <tr>
+   <th scope="row">{{Glossary("Forbidden header name")}}</th>
+   <td>no</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Sintassi">Sintassi</h2>
+
+<pre class="syntaxbox">X-Content-Type-Options: nosniff
+</pre>
+
+<h2 id="Direttive">Direttive</h2>
+
+<dl>
+ <dt><code>nosniff</code></dt>
+ <br>
+ <dd>Blocca la richiesta, se è di tipo:
+ <ul>
+  <li>"<code>style</code>" e il tipo MIME non è <code>text/css</code>;</li>
+  <li>"<code>script</code>" e il tipo MIME non appartiene ai <a href="https://html.spec.whatwg.org/multipage/scripting.html#javascript-mime-type">tipi MIME JavaScript MIME.</a></li>
+ </ul>
+ </dd>
+ <dd>Abilita il Cross-Origin Read Blockingper i seguenti tipi MIME:
+ <ul>
+  <li><code>text/html</code></li>
+  <li><code>text/plain</code></li>
+  <li><code>text/json</code>, <code>application/json</code> o qualunque altro tipo avente estensione simile a  <code>*/*+json</code></li>
+  <li><code>text/xml</code>, <code>application/xml</code> o qualunque altro tipo avente estensione simile a  <code>*/*+xml</code> ( <code>image/svg+xml</code> esclusa).</li>
+ </ul>
+ </dd>
+</dl>
+
+<h2 id="Specifiche">Specifiche</h2>
+
+<table class="standard-table">
+ <tbody>
+  <tr>
+   <th scope="col">Specification</th>
+   <th scope="col">Status</th>
+   <th scope="col">Comment</th>
+  </tr>
+  <tr>
+   <td>{{SpecName("Fetch", "#x-content-type-options-header", "X-Content-Type-Options definition")}}</td>
+   <td>{{Spec2("Fetch")}}</td>
+   <td>Initial definition</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Browser_compatibility">Browser compatibility</h2>
+
+<div class="hidden">La tavola di compatibilità in questa pagina è generata usando dati strutturati. Se desideri contribuire allo sviluppo di tali dati visita <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> e inviaci una pull request.</div>
+
+<p>{{Compat("http.headers.X-Content-Type-Options")}}</p>
+
+<h2 id="Vedi_anche">Vedi anche</h2>
+
+<ul>
+ <li>{{HTTPHeader("Content-Type")}}</li>
+ <li>La <a href="https://blogs.msdn.microsoft.com/ie/2008/09/02/ie8-security-part-vi-beta-2-update/">definizione originale</a> dell'X-Content-Type-Options di Microsoft.</li>
+ <li>Lo strumento del <a href="https://observatory.mozilla.org/">Mozilla Observatory</a> per controllare la configurazione (compreso questo header) dei siti in merito alla sicurezza</li>
+ <li><a href="https://blog.mozilla.org/security/2016/08/26/mitigating-mime-confusion-attacks-in-firefox/">Mitigare gli attacchi di tipo MIME Confusion Attacks in Firefox</a></li>
+ <li><a href="https://fetch.spec.whatwg.org/#corb">Cross-Origin Read Blocking (CORB)</a></li>
+ <li><a href="https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md">Spiegazione del CORB nei Google Docs</a></li>
+</ul>
diff --git a/files/it/web/http/headers/x-xss-protection/index.html b/files/it/web/http/headers/x-xss-protection/index.html
new file mode 100644
index 0000000000..89ef4c0bc2
--- /dev/null
+++ b/files/it/web/http/headers/x-xss-protection/index.html
@@ -0,0 +1,90 @@
+---
+title: X-XSS-Protection
+slug: Web/HTTP/Headers/X-XSS-Protection
+tags:
+  - HTTP
+  - Sicurezza
+  - XSS
+  - header
+translation_of: Web/HTTP/Headers/X-XSS-Protection
+---
+<div>{{HTTPSidebar}}</div>
+
+<p>L'header HTTP di risposta  <strong><code>X-XSS-Protection</code></strong> è una funzionalità di Internet Explorer, Chrome e Safari che impedisce alle pagine di caricarsi quando rilevano attacchi di tipo cross-site scripting reflected ({{Glossary("XSS")}}). Anche se queste protezioni sono largamente non necessarie nei browser moderni, quando i siti web implementano una  {{HTTPHeader("Content-Security-Policy")}} restrittiva che disabilita l'uso di JavaScript inline (<code>'unsafe-inline'</code>), possono ancora fornire protezione agli utenti di browser datati che non supportano {{Glossary("CSP")}}.</p>
+
+<table class="properties">
+ <tbody>
+  <tr>
+   <th scope="row">Header type</th>
+   <td>{{Glossary("Response header")}}</td>
+  </tr>
+  <tr>
+   <th scope="row">{{Glossary("Forbidden header name")}}</th>
+   <td>no</td>
+  </tr>
+ </tbody>
+</table>
+
+<h2 id="Sintassi">Sintassi</h2>
+
+<pre class="syntaxbox">X-XSS-Protection: 0
+X-XSS-Protection: 1
+X-XSS-Protection: 1; mode=block
+X-XSS-Protection: 1; report=&lt;reporting-uri&gt;
+</pre>
+
+<dl>
+ <dt>0</dt>
+ <dd>Disabilita il filtro XSS.</dd>
+ <dt>1</dt>
+ <dd>Ablita il filtro XSS (solitamente il valore di default dei browser). Se un attacco di tipo cross-site scripting viene rilevato, il browser sanitizzerà la pagina web (rimuovendo il contenuto non sicuro).</dd>
+ <dt>1; mode=block</dt>
+ <dd>Abilita il filtro XSS. Piuttosto che sanitizzare la pagina web, il browser eviterà di mostrare la pagina quando un attacco viene rilevato.</dd>
+ <dt>1; report=&lt;reporting-URI&gt;  (Solo Chromium)</dt>
+ <dd>Abilita il filtro XSS. Se un attacco di tipo cross-site scripting viene rilevato, il browser sanitizzerà la pagina e riporterà la violazione. Questo sistema utilizza la funzionalità della direttiva CSP {{CSP("report-uri")}} per segnalare la violazione.</dd>
+</dl>
+
+<h2 id="Esempio">Esempio</h2>
+
+<p>Impedisce alle pagine di caricare quando viene rilevato un attacco di tipo XSS reflected:</p>
+
+<pre class="brush: bash">X-XSS-Protection: 1; mode=block</pre>
+
+<p>PHP</p>
+
+<pre class="brush: php">header("X-XSS-Protection: 1; mode=block");</pre>
+
+<p>Apache (.htaccess)</p>
+
+<pre class="brush: bash">&lt;IfModule mod_headers.c&gt;
+  Header set X-XSS-Protection "1; mode=block"
+&lt;/IfModule&gt;</pre>
+
+<p>Nginx</p>
+
+<pre class="brush: bash">add_header "X-XSS-Protection" "1; mode=block";</pre>
+
+<h2 id="Specifiche">Specifiche</h2>
+
+<p>Non parte di nessuna specifica o bozza.</p>
+
+<h2 id="Compatibilità_Browser"><font face="x-locale-heading-primary, zillaslab, Palatino, Palatino Linotype, x-locale-heading-secondary, serif"><span style="font-size: 40px;"><strong>Compatibilità Browser</strong></span></font></h2>
+
+<p> </p>
+
+<p class="hidden">The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> and send us a pull request.</p>
+
+<p>{{Compat("http.headers.X-XSS-Protection")}}</p>
+
+<h2 id="Vedi_anche"><font face="x-locale-heading-primary, zillaslab, Palatino, Palatino Linotype, x-locale-heading-secondary, serif"><span style="font-size: 40px;"><strong>Vedi anche</strong></span></font></h2>
+
+<ul>
+ <li>{{HTTPHeader("Content-Security-Policy")}}</li>
+ <li><a href="https://blogs.msdn.microsoft.com/ieinternals/2011/01/31/controlling-the-xss-filter/">Controlling the XSS Filter – Microsoft</a></li>
+ <li><a href="https://www.virtuesecurity.com/blog/understanding-xss-auditor/">Understanding XSS Auditor – Virtue Security</a></li>
+ <li>
+  <p><a href="http://blog.innerht.ml/the-misunderstood-x-xss-protection/">The misunderstood X-XSS-Protection – blog.innerht.ml</a></p>
+ </li>
+</ul>
+
+<p> </p>