delete pages that were never translated from en-US (es, part 1) (#1547)

3 files changed, 0 insertions, 173 deletions

diff --git a/files/es/web/http/cors/errors/corsnotsupportingcredentials/index.html b/files/es/web/http/cors/errors/corsnotsupportingcredentials/index.html
deleted file mode 100644
index b27a103689..0000000000
--- a/files/es/web/http/cors/errors/corsnotsupportingcredentials/index.html
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: >-
-  Reason: Credential is not supported if the CORS header
-  ‘Access-Control-Allow-Origin’ is ‘*’
-slug: Web/HTTP/CORS/Errors/CORSNotSupportingCredentials
-translation_of: Web/HTTP/CORS/Errors/CORSNotSupportingCredentials
----
-<div>{{HTTPSidebar}}</div>
-
-<h2 id="Reason">Reason</h2>
-
-<pre class="syntaxbox">Reason: Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’</pre>
-
-<h2 id="What_went_wrong">What went wrong?</h2>
-
-<p>The {{Glossary("CORS")}} request was attempted with the credentials flag set, but the server is configured using the wildcard (<code>"*"</code>) as the value of {{HTTPHeader("Access-Control-Allow-Origin")}}, which doesn't allow the use of credentials.</p>
-
-<p>To correct this problem on the client side, simply ensure that the credentials flag's value is <code>false</code> when issuing your CORS request.</p>
-
-<ul>
- <li>If the request is being issued using {{domxref("XMLHttpRequest")}}, make sure you're not setting {{domxref("XMLHttpRequest.withCredentials", "withCredentials")}} to <code>true</code>.</li>
- <li>If using <a href="/en-US/docs/Web/API/Server-sent_events">Server-sent events</a>, make sure {{domxref("EventSource.withCredentials")}} is <code>false</code> (it's the default value).</li>
- <li>If using the <a href="/en-US/docs/Web/API/Fetch_API">Fetch API</a>, make sure {{domxref("Request.credentials")}} is <code>"omit"</code>.</li>
-</ul>
-
-<p>If, instead, you need to adjust the server's behavior, you'll need to change the value of <code>Access-Control-Allow-Origin</code> to grant access to the origin from which the client is loaded.</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/CORS/Errors">CORS errors</a></li>
- <li>Glossary: {{Glossary("CORS")}}</li>
- <li><a href="/en-US/docs/Web/HTTP/CORS">CORS introduction</a></li>
-</ul>
diff --git a/files/es/web/http/headers/accept-charset/index.html b/files/es/web/http/headers/accept-charset/index.html
deleted file mode 100644
index 26433c22db..0000000000
--- a/files/es/web/http/headers/accept-charset/index.html
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Accept-Charset
-slug: Web/HTTP/Headers/Accept-Charset
-tags:
-  - Negociación de Contenido
-translation_of: Web/HTTP/Headers/Accept-Charset
----
-<div>{{HTTPSidebar}}</div>
-
-<p>The <strong><code>Accept-Charset</code></strong> request HTTP header advertises which character set the client is able to understand. Using <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a>, the server then selects one of the proposals, uses it and informs the client of its choice within the {{HTTPHeader("Content-Type")}} response header. Browsers usually don't set this header as the default value for each content type is usually correct and transmitting it would allow easier fingerprinting.</p>
-
-<p>If the server cannot serve any matching character set, it can theoretically send back a {{HTTPStatus("406")}} (Not Acceptable) error code. But, for a better user experience, this is rarely done and the more common way is to ignore the <code>Accept-Charset</code> header in this case.</p>
-
-<div class="note">
-<p>In early versions of HTTP/1.1, a default charset (<code>ISO-8859-1</code>) was defined. This is no more the case and now each content type may have its own default.</p>
-</div>
-
-<table class="properties">
- <tbody>
-  <tr>
-   <th scope="row">Header type</th>
-   <td>{{Glossary("Request header")}}</td>
-  </tr>
-  <tr>
-   <th scope="row">{{Glossary("Forbidden header name")}}</th>
-   <td>yes</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Syntax">Syntax</h2>
-
-<pre class="syntaxbox">Accept-Charset: &lt;charset&gt;
-
-// Multiple types, weighted with the {{glossary("quality values", "quality value")}} syntax:
-Accept-Charset: utf-8, iso-8859-1;q=0.5</pre>
-
-<h2 id="Directives">Directives</h2>
-
-<dl>
- <dt><code>&lt;charset&gt;</code></dt>
- <dd>Un conjunto de caracteres como <code>utf-8</code> o <code>iso-8859-15.</code></dd>
- <dt><code>*</code></dt>
- <dd>Any charset not mentioned elsewhere in the header; <code>'*'</code> being used as a wildcard.</dd>
- <dt><code>;q=</code> (q-factor weighting)</dt>
- <dd>Any value is placed in an order of preference expressed using a relative <a href="/en-US/docs/Glossary/Quality_values">quality value</a> called the <em>weight</em>.</dd>
-</dl>
-
-<h2 id="Examples">Examples</h2>
-
-<pre>Accept-Charset: iso-8859-1
-
-Accept-Charset: utf-8, iso-8859-1;q=0.5
-
-Accept-Charset: utf-8, iso-8859-1;q=0.5, *;q=0.1
-</pre>
-
-<h2 id="Especificaciones">Especificaciones</h2>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th scope="col">Especificación</th>
-   <th scope="col">Título</th>
-  </tr>
-  <tr>
-   <td>{{RFC("7231", "Accept-Charset", "5.3.3")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Context</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Compatibilidad_del_navegador">Compatibilidad del navegador</h2>
-
-
-
-<p>{{Compat("http.headers.Accept-Charset")}}</p>
-
-<h2 id="También_puedes_revisar">También puedes revisar:</h2>
-
-<ul>
- <li>HTTP <a href="/en-US/docs/Web/HTTP/Content_negotiation">content negotiation</a></li>
- <li>Encabezados conlos resultados de la negociación de contenido: {{HTTPHeader("Content-Type")}}</li>
- <li>Otros encabezados similares: {{HTTPHeader("TE")}}, {{HTTPHeader("Accept-Encoding")}}, {{HTTPHeader("Accept-Language")}}, {{HTTPHeader("Accept")}}</li>
-</ul>
diff --git a/files/es/web/http/status/301/index.html b/files/es/web/http/status/301/index.html
deleted file mode 100644
index 496fb038f3..0000000000
--- a/files/es/web/http/status/301/index.html
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: 301 Movido Permanentemente
-slug: Web/HTTP/Status/301
-translation_of: Web/HTTP/Status/301
----
-<div>{{HTTPSidebar}}</div>
-
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>301 Moved Permanently</strong></code> redirect status response code indicates that the resource requested has been definitively moved to the URL given by the {{HTTPHeader("Location")}} headers. A browser redirects to this page and search engines update their links to the resource (in 'SEO-speak', it is said that the 'link-juice' is sent to the new URL).</p>
-
-<p>Even if the specification requires the method (and the body) not to be altered when the redirection is performed, not all user-agents align with it - you can still find this type of bugged software out there. It is therefore recommended to use the <code>301</code> code only as a response for {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}} methods and to use the {{HTTPStatus("308", "308 Permanent Redirect")}} for {{HTTPMethod("POST")}} methods instead, as the method change is explicitly prohibited with this status.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="syntaxbox">301 Moved Permanently</pre>
-
-<h2 id="Example">Example</h2>
-
-<h3 id="Client_request">Client request</h3>
-
-<pre>GET /index.php HTTP/1.1
-Host: www.example.org</pre>
-
-<h3 id="Server_response">Server response</h3>
-
-<pre>HTTP/1.1 301 Moved Permanently
-Location: http://www.example.org/index.asp</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
-  <tr>
-   <td>{{RFC("7231", "301 Moved Permanently" , "6.4.2")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-
-
-<p>{{Compat("http.status.301")}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPStatus("308", "308 Permanent Redirect")}}</li>
- <li>{{HTTPStatus("302", "302 Found")}}, the temporary redirect</li>
-</ul>