remove retired locales (#699)

13 files changed, 0 insertions, 766 deletions

diff --git a/files/tr/web/http/status/200/index.html b/files/tr/web/http/status/200/index.html
deleted file mode 100644
index a0f72e76f1..0000000000
--- a/files/tr/web/http/status/200/index.html
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: 200 OK
-slug: Web/HTTP/Status/200
-tags:
-  - 200OK nedir
-  - 200OK oluşturma
-translation_of: Web/HTTP/Status/200
----
-<div>{{HTTPSidebar}}</div>
-
-<p>HTTP cevap durum kodu <strong><code>200 OK</code></strong>  isteğin başarılı olduğunu ifade eder. Bu durum koduna sahip cevaplar, varsayılan olarak önbelleğe (cache) alınabilir.</p>
-
-<p>Başarılı isteğin ne anlama geldiği, yapılan HTTP isteğin türüne bağlıdır:</p>
-
-<ul>
- <li>{{HTTPMethod("GET")}}: İstenilen kaynak bulundu ve dönen cevabın gövdesinde gönderildi.</li>
- <li>{{HTTPMethod("HEAD")}}: Bütün başlık mesajları (HEADER) cevabın gövdesi olarak döner.</li>
- <li>{{HTTPMethod("POST")}}: Yapılan isteğe karşılık gelen sonuç, cevabın gövdesinde gönderilir.</li>
- <li>{{HTTPMethod("TRACE")}}: Sunucu, aldığı isteği cevabın gövdesi olarak gönderir.</li>
-</ul>
-
-<p>Başarılı olan {{HTTPMethod("PUT")}} veya {{HTTPMethod("DELETE")}} isteği sonucunda dönen cevap genellikle <code>200</code> <code>OK</code> değil, <code>{{HTTPStatus("204")}}</code><code>No Content (veya bir kaynak ilk kez oluşturulmuşsa {{HTTPStatus("201")}}) Created)</code> olur.</p>
-
-<h2 id="Durum">Durum</h2>
-
-<pre class="syntaxbox notranslate">200 OK</pre>
-
-<h2 id="Şartnameler">Şartnameler</h2>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
-  <tr>
-   <td>{{RFC("7231", "200 OK" , "6.3.1")}}</td>
-   <td>Hypertext Transfer Protokolü (HTTP/1.1): Anlam ve İçerikler</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Tarayıcı_Uyumluluğu">Tarayıcı Uyumluluğu</h2>
-
-<p class="hidden">Tarayıcı uyumluluğu tablosu, hazır verilerden otomatik olarak oluşturulmuştur. Eğer bu verilere katkıda bulunmak isteseniz, <a href="https://github.com/mdn/browser-compat-data">https://github.com/mdn/browser-compat-data</a> adresine gidin ve bize bir çekme isteğinde (pull request) bulunun.</p>
-
-<p>{{Compat("http.status.200")}}</p>
-
-<h2 id="Ayrıca_bakınız">Ayrıca bakınız</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Methods">HTTP istek metodları</a></li>
-</ul>
diff --git a/files/tr/web/http/status/205/index.html b/files/tr/web/http/status/205/index.html
deleted file mode 100644
index d212490377..0000000000
--- a/files/tr/web/http/status/205/index.html
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: 205 Reset Content
-slug: Web/HTTP/Status/205
-translation_of: Web/HTTP/Status/205
----
-<p>{{HTTPSidebar}}</p>
-
-<p>The HTTP <strong><code>205 Reset Content</code></strong> response status tells the client to reset the document view, so for example to clear the content of a form, reset a canvas state, or to refresh the UI.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="syntaxbox">205 Reset Content</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", "205 Reset Content" , "6.3.6")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Compatibility_Notes">Compatibility Notes</h2>
-
-<ul>
- <li>Browser behavior differs if this response erroneously includes a body on persistent connections See <a href="/en-US/docs/Web/HTTP/Status/204">204 No Content</a> for more detail.</li>
-</ul>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPStatus(204)}} No Content</li>
-</ul>
diff --git a/files/tr/web/http/status/301/index.html b/files/tr/web/http/status/301/index.html
deleted file mode 100644
index a2dcab9a0d..0000000000
--- a/files/tr/web/http/status/301/index.html
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: 301 Kalıcı Yönlendirme
-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 notranslate">301 Moved Permanently</pre>
-
-<h2 id="Example">Example</h2>
-
-<h3 id="Client_request">Client request</h3>
-
-<pre class="notranslate">GET /index.php HTTP/1.1
-Host: www.example.org</pre>
-
-<h3 id="Server_response">Server response</h3>
-
-<pre class="notranslate">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>
- <li><a href="https://www.exai.com/blog/301-redirects">301 Redirect </a></li>
-</ul>
diff --git a/files/tr/web/http/status/302/index.html b/files/tr/web/http/status/302/index.html
deleted file mode 100644
index 061e7bfaa2..0000000000
--- a/files/tr/web/http/status/302/index.html
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: 302 Geçici Yönlendirme
-slug: Web/HTTP/Status/302
-translation_of: Web/HTTP/Status/302
----
-<div>{{HTTPSidebar}}</div>
-
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>302 Found</strong></code> redirect status response code indicates that the resource requested has been temporarily moved to the URL given by the {{HTTPHeader("Location")}} header. A browser redirects to this page but search engines don't update their links to the resource (in 'SEO-speak', it is said that the 'link-juice' is not 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 conform here - you can still find this type of bugged software out there. It is therefore recommended to set the <code>302</code> code only as a response for {{HTTPMethod("GET")}} or {{HTTPMethod("HEAD")}} methods and to use {{HTTPStatus("307", "307 Temporary Redirect")}} instead, as the method change is explicitly prohibited in that case.</p>
-
-<p>In the cases where you want the method used to be changed to {{HTTPMethod("GET")}}, use {{HTTPStatus("303", "303 See Other")}} instead. This is useful when you want to give a response to a {{HTTPMethod("PUT")}} method that is not the uploaded resource but a confirmation message such as: 'you successfully uploaded XYZ'.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="syntaxbox notranslate">302 Found</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7231", "302 Found" , "6.4.3")}}</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.302")}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPStatus("307", "307 Temporary Redirect")}}, the equivalent of this status code where the method used never changes.</li>
- <li>{{HTTPStatus("303", "303 See Other")}}, a temporary redirect that changes the method used to {{HTTPMethod("GET")}}.</li>
- <li>{{HTTPStatus("301", "301 Moved Permanently")}}, the permanent redirect.</li>
-</ul>
diff --git a/files/tr/web/http/status/400/index.html b/files/tr/web/http/status/400/index.html
deleted file mode 100644
index 2d6f8ea50a..0000000000
--- a/files/tr/web/http/status/400/index.html
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: 400 Kötü İstek
-slug: Web/HTTP/Status/400
-translation_of: Web/HTTP/Status/400
----
-<p>{{HTTPSidebar}}</p>
-
-<p>The HyperText Transfer Protocol (HTTP) <code><strong>400 Bad Request</strong></code> response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).</p>
-
-<div class="warning">
-<p>The client should not repeat this request without modification.</p>
-</div>
-
-<h2 id="Status">Status</h2>
-
-<pre class="syntaxbox notranslate">400 Bad Request </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", "400 Bad Request" , "6.5.1")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="See_Also">See Also</h2>
-
-<ul>
- <li><a href="https://www.exai.com/blog/400-bad-request-error">400 Bad Request </a></li>
-</ul>
diff --git a/files/tr/web/http/status/401/index.html b/files/tr/web/http/status/401/index.html
deleted file mode 100644
index 1eb6e7c0d7..0000000000
--- a/files/tr/web/http/status/401/index.html
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: 401 Yetkisiz
-slug: Web/HTTP/Status/401
-translation_of: Web/HTTP/Status/401
----
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP <strong><code>401 Unauthorized</code></strong> client error status response code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource.</p>
-
-<p>This status is sent with a {{HTTPHeader("WWW-Authenticate")}} header that contains information on how to authorize correctly.</p>
-
-<p>This status is similar to {{HTTPStatus("403")}}, but in this case, authentication is possible.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="syntaxbox notranslate">401 Unauthorized</pre>
-
-<h2 id="Example_response">Example response</h2>
-
-<pre class="notranslate">HTTP/1.1 401 Unauthorized
-Date: Wed, 21 Oct 2015 07:28:00 GMT
-WWW-Authenticate: Basic realm="Access to staging site"</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("7235", "401 Unauthorized" , "3.1")}}</td>
-   <td>HTTP/1.1: Authentication</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</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.status.401")}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a></li>
- <li>{{HTTPHeader("WWW-Authenticate")}}</li>
- <li>{{HTTPHeader("Authorization")}}</li>
- <li>{{HTTPHeader("Proxy-Authorization")}}</li>
- <li>{{HTTPHeader("Proxy-Authenticate")}}</li>
- <li>{{HTTPStatus("403")}}, {{HTTPStatus("407")}}</li>
-</ul>
diff --git a/files/tr/web/http/status/402/index.html b/files/tr/web/http/status/402/index.html
deleted file mode 100644
index bc74ce45f1..0000000000
--- a/files/tr/web/http/status/402/index.html
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: 402 Ödeme Gerekli
-slug: Web/HTTP/Status/402
-translation_of: Web/HTTP/Status/402
----
-<div>{{HTTPSidebar}}{{SeeCompatTable}}</div>
-
-<p>The HTTP <strong><code>402 Payment Required</code></strong> is a nonstandard client error status response code that is reserved for future use.</p>
-
-<p>Sometimes, this code indicates that the request can not be processed until the client makes a payment. Originally it was created to enable digital cash or (micro) payment systems and would indicate that the requested content is not available until the client makes a payment. However, no standard use convention exists and different entities use it in different contexts.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="syntaxbox notranslate">402 Payment Required</pre>
-
-<h2 id="Example_response">Example response</h2>
-
-<pre class="brush: bash notranslate">HTTP/1.1 402 Payment Required
-Date: Wed, 21 Oct 2015 07:28:00 GMT
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7231", "402 Payment Required" , "6.5.2")}}</td>
-   <td>HTTP/1.1: Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</h2>
-
-
-
-<p>{{Compat("http.status.402")}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li><a href="/en-US/docs/Web/HTTP/Authentication">HTTP authentication</a></li>
-</ul>
diff --git a/files/tr/web/http/status/403/index.html b/files/tr/web/http/status/403/index.html
deleted file mode 100644
index e167459808..0000000000
--- a/files/tr/web/http/status/403/index.html
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: 403 Yasaklı
-slug: Web/HTTP/Status/403
-translation_of: Web/HTTP/Status/403
----
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP <strong><code>403 Forbidden</code></strong> client error status response code indicates that the server understood the request but refuses to authorize it.</p>
-
-<p>This status is similar to {{HTTPStatus("401")}}, but in this case, re-authenticating will make no difference. The access is permanently forbidden and tied to the application logic, such as insufficient rights to a resource.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="syntaxbox notranslate">403 Forbidden</pre>
-
-<h2 id="Example_response">Example response</h2>
-
-<pre class="notranslate">HTTP/1.1 403 Forbidden
-Date: Wed, 21 Oct 2015 07:28:00 GMT
-</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7231", "403 Forbidden" , "6.5.3")}}</td>
-   <td>HTTP/1.1: Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</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.status.403")}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPStatus("401")}}</li>
- <li><a href="https://kinsta.com/blog/403-forbidden-error/">403 forbidden error</a></li>
- <li><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html" rel="noopener">HTTP/1.1: Status Code Definitions</a></li>
- <li><a href="https://www.exai.com/blog/403-forbidden">403 forbidden </a></li>
-</ul>
diff --git a/files/tr/web/http/status/404/index.html b/files/tr/web/http/status/404/index.html
deleted file mode 100644
index 15189bdf9f..0000000000
--- a/files/tr/web/http/status/404/index.html
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: 404 Bulunamadı
-slug: Web/HTTP/Status/404
-translation_of: Web/HTTP/Status/404
----
-<div>{{HTTPSidebar}}</div>
-
-<p>The HTTP <code><strong>404 Not Found</strong></code> client error response code indicates that the server can't find the requested resource. Links which lead to a 404 page are often called broken or dead links, and can be subject to <a href="https://en.wikipedia.org/wiki/Link_rot">link rot</a>.</p>
-
-<p>A 404 status code does not indicate whether the resource is temporarily or permanently missing. But if a resource is permanently removed, a {{HTTPStatus("410")}} (Gone) should be used instead of a 404 status.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="syntaxbox notranslate">404 Not Found</pre>
-
-<h2 id="Custom_error_pages">Custom error pages</h2>
-
-<p>Many web sites customize the look of a 404 page to be more helpful to the user and provide guidance on what to do next. Apache servers can be configured using an <code>.htaccess</code> file and a code snippet like the following example.</p>
-
-<pre class="brush: bash notranslate">ErrorDocument 404 /notfound.html</pre>
-
-<p>For an example of a custom 404 page, see <a href="https://developer.mozilla.org/en-US/404">MDN's 404 page</a>.</p>
-
-<div class="note">
-<p>Custom design is a good thing, in moderation. Feel free to make your 404 page humorous and human, but don't confuse your users.</p>
-</div>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7231", "404 Not Found" , "6.5.4")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</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.status.404")}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{HTTPStatus("410")}}</li>
- <li>
-  <p>{{interwiki("wikipedia", "HTTP_404", "Wikipedia: HTTP 404")}}</p>
- </li>
- <li>
-  <p><a class="external" href="https://www.exai.com/blog/404-http-error" rel="noopener">404 Error </a></p>
- </li>
-</ul>
diff --git a/files/tr/web/http/status/405/index.html b/files/tr/web/http/status/405/index.html
deleted file mode 100644
index ef06ed441a..0000000000
--- a/files/tr/web/http/status/405/index.html
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: 405 İzin Verilmeyen Metot
-slug: Web/HTTP/Status/405
-tags:
-  - Durum kodu
-translation_of: Web/HTTP/Status/405
----
-<div>{{HTTPSidebar}}</div>
-
-<p>HyperText Transfer Protocol (HTTP) <code><strong>405 Method Not Allowed</strong></code> durum kodu sunucunun istek metodunu bilmesine rağmen istenen kaynak tarafından metodun desteklenmediği anlamına gelir.</p>
-
-<p class="newpage">Sunucu MUTLAKA <strong><code>Allow</code></strong> başlığı ile istenen kaynağın şu an desteklediği metotları listeleyen bir 405 cevabı vermelidir.</p>
-
-<h2 id="Durum">Durum</h2>
-
-<pre class="syntaxbox notranslate">405 Method Not Allowed</pre>
-
-<h2 id="Detaylar">Detaylar</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("7231", "405 Method Not Allowed" , "6.5.5")}}</td>
-   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Bakınız">Bakınız</h2>
-
-<ul>
- <li>{{HTTPHeader("Allow")}}</li>
- <li><a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html" rel="noopener">HTTP/1.1: Status Code Definitions</a></li>
- <li><a href="https://kinsta.com/blog/405-method-not-allowed-error/">How to Fix 405 Method Not Allowed</a></li>
- <li><a href="https://docs.microsoft.com/en-us/aspnet/web-api/overview/testing-and-debugging/troubleshooting-http-405-errors-after-publishing-web-api-applications">Troubleshooting HTTP 405</a></li>
-</ul>
diff --git a/files/tr/web/http/status/418/index.html b/files/tr/web/http/status/418/index.html
deleted file mode 100644
index 14ec22a3aa..0000000000
--- a/files/tr/web/http/status/418/index.html
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: 418 Ben Çaydanlığım
-slug: Web/HTTP/Status/418
-translation_of: Web/HTTP/Status/418
----
-<p>{{HTTPSidebar}}</p>
-
-<p>The HTTP <strong><code>418 I'm a teapot</code></strong> client error response code indicates that the server refuses to brew coffee because it is, permanently, a teapot. A combined coffee/tea pot that is temporarily out of coffee should instead return 503. This error is a reference to Hyper Text Coffee Pot Control Protocol defined in April Fools' jokes in 1998 and 2014.</p>
-
-<h2 id="Status">Status</h2>
-
-<pre class="syntaxbox notranslate">418 I'm a teapot</pre>
-
-<h2 id="Specifications">Specifications</h2>
-
-<table class="standard-table">
- <thead>
-  <tr>
-   <th scope="col">Specification</th>
-   <th scope="col">Title</th>
-  </tr>
- </thead>
- <tbody>
-  <tr>
-   <td>{{RFC("2324", "418 I'm a teapot" , "2.3.2")}}</td>
-   <td>Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0): Semantics and Content</td>
-  </tr>
-  <tr>
-   <td>{{RFC("7168", "418 I'm a teapot" , "2.3.3")}}</td>
-   <td>The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA): Response Codes</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Browser_compatibility">Browser compatibility</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.status.418")}}</p>
-
-<h2 id="See_also">See also</h2>
-
-<ul>
- <li>{{interwiki("wikipedia", "Hyper Text Coffee Pot Control Protocol", "Wikipedia: Hyper Text Coffee Pot Control Protocol")}}</li>
-</ul>
diff --git a/files/tr/web/http/status/500/index.html b/files/tr/web/http/status/500/index.html
deleted file mode 100644
index 30f4e0fa77..0000000000
--- a/files/tr/web/http/status/500/index.html
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: 500 İç Sunucu Hatası
-slug: Web/HTTP/Status/500
-tags:
-  - Durum kodu
-  - HTTP
-  - Sunucu hatası
-translation_of: Web/HTTP/Status/500
----
-<div>{{HTTPSidebar}}</div>
-
-<p>HTTP <code><strong>500 İç Sunucu Hatası</strong></code> <span id="result_box" lang="tr"><span>sunucu hata yanıt kodu, sunucunun isteği yerine getirmesini engelleyen beklenmedik bir durumla karşılaştığını gösterir.</span></span></p>
-
-<p><span id="result_box" lang="tr"><span>Bu hata yanıtı genel bir "tümünü yakalama" yanıtıdır.</span> <span>Çoğu zaman sunucu yöneticileri, hatanın gelecekte tekrar oluşmasını önlemek için 500 durum kodu gibi hata yanıtlarını günlüğe kaydederler.</span></span></p>
-
-<h2 id="Durum">Durum</h2>
-
-<pre class="syntaxbox">500 İç Sunucu Hatası</pre>
-
-<h2 id="Tanımlar">Tanımlar</h2>
-
-<table class="standard-table">
- <tbody>
-  <tr>
-   <th scope="col">Tanım</th>
-   <th scope="col">Başlık</th>
-  </tr>
-  <tr>
-   <td>{{RFC("7231", "500 Internal Server Error" , "6.6.1")}}</td>
-   <td>Köprü Metni Aktarım Protokolü (HTTP / 1.1): Anlambilim ve İçerik</td>
-  </tr>
- </tbody>
-</table>
-
-<h2 id="Tarayıcı_uyumluluğu">Tarayıcı uyumluluğu</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.status.500")}}</p>
diff --git a/files/tr/web/http/status/index.html b/files/tr/web/http/status/index.html
deleted file mode 100644
index 68c768ecc5..0000000000
--- a/files/tr/web/http/status/index.html
+++ /dev/null
@@ -1,193 +0,0 @@
----
-title: HTTP yanıt durumu kodları
-slug: Web/HTTP/Status
-tags:
-  - HTTP
-  - NeedsTranslation
-  - Status codes
-  - TopicStub
-translation_of: Web/HTTP/Status
----
-<div>{{HTTPSidebar}}</div>
-
-<p>HTTP yanıt durumu kodları belirli bir <a href="/tr/docs/Web/HTTP">HTTP</a> isteğinin başarıyla tamamlanıp tamamlanmadığını gösterir. Yanıtları beş sınıfa ayrılır:<br>
- <br>
- 1. Bilgilendirme yanıtları (100-199),<br>
- 2. Başarı yanıtları (200-299),<br>
- 3. Yönlendirmeler (300-399),<br>
- 4. İstemci hataları (400-499) ve,<br>
- 5. Sunucu hataları (500-599).</p>
-
-<p>Durum kodları<a href="https://tools.ietf.org/html/rfc2616#section-10"> RFC 2616 bölüm 10</a>'da tanımlanmıştır. Güncellenmiş bir özelliği <a href="https://tools.ietf.org/html/rfc7231#section-6.5.1">RFC 7231</a>'de bulabilirsiniz.</p>
-
-<div class="blockIndicator note">
-<p>Bu listede olmayan bir yanıt alırsanız, bu, muhtemelen sunucunun yazılımına özel, standart dışı bir yanıttır.</p>
-
-<p>Cevaplar (İngilizce) Orjinal olarak döndürüleceğinden - cevabın Türkçesi yanında verilmiştir. </p>
-</div>
-
-<h2 id="Bilgilendirme_yanıtları">Bilgilendirme yanıtları</h2>
-
-<dl>
- <dt>{{HTTPStatus(100, "100 Continue")}} - "100 Devam et"</dt>
- <dd>Bu ara cevap, şu ana kadar her şeyin yolunda gittiğini ve müşterinin isteğine devam etmesi ya da bitmişse bu bilgiyi yoksayması gerektiğini gösterir.</dd>
- <dt>{{HTTPStatus(101, "101 101 Switching Protocol")}} - "101 Protokol Değiştiriliyor"</dt>
- <dd>Bu kod istemci tarafından gönderilen istekteki {{HTTPHeader("Upgrade")}} başlığına yanıt olarak gönderilir ve sunucunun hangi protokole geçtiğini belirtir.</dd>
- <dt>{{HTTPStatus(102, "102 Processing")}} ({{Glossary("WebDAV")}}) - "102 İşleniyor" - Sözlük("WebDAV") </dt>
- <dd>Bu kod sunucunun isteği aldığını ve işlemekte olduğunu ancak henüz yanıt vermediğini bildirir.<br>
- <strong>WebDAV(Web Distributed Authoring and Versioning</strong><strong>):</strong> World Wide Web sunucularında depolanmış belge ve dosyaları düzenleme ve yönetmede kullanıcılar arasında iş birliğini kolaylaştıran bir Hiper Metin Aktarım Protokolü uzantısıdır.</dd>
- <dt>{{HTTPStatus(103, "103 Early Hints")}} -"103 Ön İpucu"</dt>
- <dd>Bu durum kodunun esas olarak {{HTTPHeader ("Link")}} başlığıyla kullanılması amaçlanmıştır ve sunucu bir yanıt hazırlarken kullanıcı aracısının kaynakları <a href="https://wiki.developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content">önyüklemeye</a> başlamasını sağlar.</dd>
-</dl>
-
-<h2 id="Başarı_yanıtları">Başarı yanıtları</h2>
-
-<dl>
- <dt>{{HTTPStatus(200, "200 Tamam")}}</dt>
- <dd>İstek başarılı oldu. Buradaki başarı, HTTP metoduna göre  farklı anlamlara gelir:<br>
- GET: Kaynak alındı ve mesaj gövdesinde iletildi.<br>
- HEAD: Varlık başlıkları mesaj gövdesindedir.<br>
- PUT veya POST: Eylemin sonucunu açıklayan kaynak mesaj gövdesinde iletildi.<br>
- TRACE: Mesaj gövdesinde sunucu tarafından alındığı şekliyle istek mesajı bulunuyor.</dd>
- <dt>{{HTTPStatus(201, "201 Oluşturuldu")}}</dt>
- <dd>"İstek başarılı oldu ve bunun sonucunda yeni bir kaynak oluşturuldu."<br>
- Genellikle POST veya PUT isteklerinden sonra gönderilen yanıt budur.</dd>
- <dt>{{HTTPStatus(202, "202 Kabul edildi")}}</dt>
- <dd>"Talep alındı, ancak henüz işlem yapılmadı." HTTP'de daha sonra isteğin sonucunu belirten eşzamansız(asenkron) bir yanıt göndermenin bir yolu olmadığından, kesin değildir.<br>
- 'Başka bir işlemin yapıldığı' veya<br>
- 'Sunucunun isteği işlediği durumlar' için veya<br>
- 'toplu işleme' yanıt olarak tasarlanmıştır.(toplu işleme: bir defada -bölünmeden- yapılacak işlem bloğu) </dd>
- <dt>{{HTTPStatus(203, "203 Non-Authoritative Information")}} - "203 Yetkili Olmayan Bilgiler"-</dt>
- <dd>Bu yanıt kodu, döndürülen meta bilginin, kaynak sunucudakiyle tam olarak aynı olmadığı, ancak yerel veya üçüncü taraf bir kopyadan toplandığı anlamına gelir. Bu özel durum haricinde, "200 OK" yanıtı tercih edilir.</dd>
- <dt>{{HTTPStatus(204, "204 No Content")}} - "204 İçerik Yok"</dt>
- <dd>Bu istek için gönderilecek içerik yok, ancak başlıklar faydalı olabilir. Kullanıcı aracısı, bu kaynak için önbelleğe alınmış başlıklarını yenileriyle güncelleyebilir.</dd>
- <dt>{{HTTPStatus(205, "205 Reset Content")}} - "205 İçeriği Sıfırla"</dt>
- <dd>Kullanıcı aracısına bu isteği gönderen belgeyi sıfırlamasını söyler.</dd>
- <dt>{{HTTPStatus(206, "206 Partial Content")}} - "206 Kısmi İçerik"</dt>
- <dd>This response code is used because of range header sent by the client to separate download into multiple streams.</dd>
- <dt>{{HTTPStatus(207, "207 Multi-Status")}} ({{Glossary("WebDAV")}}) - "207 Birden fazla durum" - Sözlük("WebDAV") </dt>
- <dd>Birden çok durum kodunun uygun olabileceği durumlar için birden çok kaynak hakkında bilgi aktarır.</dd>
- <dt>{{HTTPStatus(208, "208 Already Reported")}} ({{Glossary("WebDAV")}}) - "208 Rapor edilmiş" - Sözlük("WebDAV") </dt>
- <dd>Bir <code>&lt;dav:propstat&gt;</code> yanıt öğesinin içinde, birden çok bağlamanın dahili üyelerinin aynı koleksiyona tekrar tekrar numaralandırılmasını önlemek için kullanılır.</dd>
- <dt>{{HTTPStatus(226, "226 IM Used")}} (<a href="https://tools.ietf.org/html/rfc3229">HTTP Delta şifrelemesi</a>) - "Kullanılmış IM Başlığı"</dt>
- <dd>Sunucu, kaynak için bir <code>GET</code> isteğini yerine getirdi ve yanıt, geçerli örneğe uygulanan bir veya daha fazla örnek işlemenin sonucunun bir temsilidir.<br>
- IM = <a href="https://tools.ietf.org/html/rfc3229#section-10.1">instance-manipulation</a> : örnek işleme</dd>
-</dl>
-
-<h2 id="Yönlendirme_mesajları">Yönlendirme mesajları</h2>
-
-<dl>
- <dt>{{HTTPStatus(300, "300 Multiple Choice")}}</dt>
- <dd>The request has more than one possible responses. User-agent or user should choose one of them. There is no standardized way to choose one of the responses.</dd>
- <dt>{{HTTPStatus(301, "301 Kalıcı Yönlendirme")}}</dt>
- <dd>This response code means that URI of requested resource has been changed. Probably, new URI would be given in the response.</dd>
- <dt>{{HTTPStatus(302, "302 Geçici Yönlendirme")}}</dt>
- <dd>This response code means that URI of requested resource has been changed <em>temporarily</em>. New changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.</dd>
- <dt>{{HTTPStatus(303, "303 See Other")}}</dt>
- <dd>Server sent this response to directing client to get requested resource to another URI with an GET request.</dd>
- <dt>{{HTTPStatus(304, "304 Not Modified")}}</dt>
- <dd>This is used for caching purposes. It is telling to client that response has not been modified. So, client can continue to use same cached version of response.</dd>
- <dt><code>305 Use Proxy</code> {{deprecated_inline}}</dt>
- <dd>Was defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. It has been deprecated due to security concerns regarding in-band configuration of a proxy.</dd>
- <dt><code>306 unused</code></dt>
- <dd>This response code is no longer used, it is just reserved currently. It was used in a previous version of the HTTP 1.1 specification.</dd>
- <dt>{{HTTPStatus(307, "307 Temporary Redirect")}}</dt>
- <dd>Server sent this response to directing client to get requested resource to another URI with same method that used prior request. This has the same semantic than the <code>302 Found</code> HTTP response code, with the exception that the user agent <em>must not</em> change the HTTP method used: if a <code>POST</code> was used in the first request, a <code>POST</code> must be used in the second request.</dd>
- <dt>{{HTTPStatus(308, "308 Permanent Redirect")}}</dt>
- <dd>This means that the resource is now permanently located at another URI, specified by the <code>Location:</code> HTTP Response header. This has the same semantics as the <code>301 Moved Permanently</code> HTTP response code, with the exception that the user agent <em>must not</em> change the HTTP method used: if a <code>POST</code> was used in the first request, a <code>POST</code> must be used in the second request.</dd>
-</dl>
-
-<h2 id="İstemci_hatası_yanıtları">İstemci hatası yanıtları</h2>
-
-<dl>
- <dt>{{HTTPStatus(400, "400 Bad Request")}}</dt>
- <dd>This response means that server could not understand the request due to invalid syntax.</dd>
- <dt>{{HTTPStatus(401, "401 Unauthorized")}}</dt>
- <dd>Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.</dd>
- <dt><code>402 Payment Required</code></dt>
- <dd>This response code is reserved for future use. Initial aim for creating this code was using it for digital payment systems however this is not used currently.</dd>
- <dt>{{HTTPStatus(403, "403 Forbidden")}}</dt>
- <dd>The client does not have access rights to the content, i.e. they are unauthorized, so server is rejecting to give proper response. Unlike 401, the client's identity is known to the server.</dd>
- <dt>{{HTTPStatus(404, "404 Not Found")}}</dt>
- <dd>The server can not find requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client. This response code is probably the most famous one due to its frequent occurence on the web.</dd>
- <dt>{{HTTPStatus(405, "405 Method Not Allowed")}}</dt>
- <dd>The request method is known by the server but has been disabled and cannot be used. For example, an API may forbid DELETE-ing a resource. The two mandatory methods, <code>GET</code> and <code>HEAD</code>, must never be disabled and should not return this error code.</dd>
- <dt>{{HTTPStatus(406, "406 Not Acceptable")}}</dt>
- <dd>This response is sent when the web server, after performing <a href="/en-US/docs/HTTP/Content_negotiation#Server-driven_negotiation">server-driven content negotiation</a>, doesn't find any content following the criteria given by the user agent.</dd>
- <dt>{{HTTPStatus(407, "407 Proxy Authentication Required")}}</dt>
- <dd>This is similar to 401 but authentication is needed to be done by a proxy.</dd>
- <dt>{{HTTPStatus(408, "408 Request Timeout")}}</dt>
- <dd>This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.</dd>
- <dt>{{HTTPStatus(409, "409 Conflict")}}</dt>
- <dd>This response is sent when a request conflicts with the current state of the server.</dd>
- <dt>{{HTTPStatus(410, "410 Gone")}}</dt>
- <dd>This response would be sent when the requested content has been permenantly deleted from server, with no forwarding address. Clients are expected to remove their caches and links to the resource. The HTTP specification intends this status code to be used for "limited-time, promotional services". APIs should not feel compelled to indicate resources that have been deleted with this status code.</dd>
- <dt>{{HTTPStatus(411, "411 Length Required")}}</dt>
- <dd>Server rejected the request because the <code>Content-Length</code> header field is not defined and the server requires it.</dd>
- <dt>{{HTTPStatus(412, "412 Precondition Failed")}}</dt>
- <dd>The client has indicated preconditions in its headers which the server does not meet.</dd>
- <dt>{{HTTPStatus(413, "413 Payload Too Large")}}</dt>
- <dd>Request entity is larger than limits defined by server; the server might close the connection or return an <code>Retry-After</code> header field.</dd>
- <dt>{{HTTPStatus(414, "414 URI Too Long")}}</dt>
- <dd>The URI requested by the client is longer than the server is willing to interpret.</dd>
- <dt>{{HTTPStatus(415, "415 Unsupported Media Type")}}</dt>
- <dd>The media format of the requested data is not supported by the server, so the server is rejecting the request.</dd>
- <dt>{{HTTPStatus(416, "416 Requested Range Not Satisfiable")}}</dt>
- <dd>The range specified by the <code>Range</code> header field in the request can't be fulfilled; it's possible that the range is outside the size of the target URI's data.</dd>
- <dt>{{HTTPStatus(417, "417 Expectation Failed")}}</dt>
- <dd>This response code means the expectation indicated by the <code>Expect</code> request header field can't be met by the server.</dd>
- <dt>{{HTTPStatus(418, "418 I'm a teapot")}}</dt>
- <dd>The server refuses the attempt to brew coffee with a teapot.</dd>
- <dt>{{HTTPStatus(421, "421 Misdirected Request")}}</dt>
- <dd>The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.</dd>
- <dt>{{HTTPStatus(422, "422 Unprocessable Entity")}} ({{Glossary("WebDAV")}})</dt>
- <dd>The request was well-formed but was unable to be followed due to semantic errors.</dd>
- <dt>{{HTTPStatus(423, "423 Locked")}} ({{Glossary("WebDAV")}})</dt>
- <dd>The resource that is being accessed is locked.</dd>
- <dt>{{HTTPStatus(424, "424 Failed Dependency")}} ({{Glossary("WebDAV")}})</dt>
- <dd>The request failed due to failure of a previous request.</dd>
- <dt>{{HTTPStatus(426, "426 Upgrade Required")}}</dt>
- <dd>The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an {{HTTPHeader("Upgrade")}} header in a 426 response to indicate the required protocol(s).</dd>
- <dt>{{HTTPStatus(428, "428 Precondition Required")}}</dt>
- <dd>The origin server requires the request to be conditional. Intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.</dd>
- <dt>{{HTTPStatus(429, "429 Too Many Requests")}}</dt>
- <dd>The user has sent too many requests in a given amount of time ("rate limiting").</dd>
- <dt>{{HTTPStatus(431, "431 Request Header Fields Too Large")}}</dt>
- <dd>The server is unwilling to process the request because its header fields are too large. The request MAY be resubmitted after reducing the size of the request header fields.</dd>
- <dt>{{HTTPStatus(451, "451 Unavailable For Legal Reasons")}}</dt>
- <dd>The user requests an illegal resource, such as a web page censored by a government.</dd>
-</dl>
-
-<h2 id="Sunucu_hatası_yanıtları">Sunucu hatası yanıtları</h2>
-
-<dl>
- <dt>{{HTTPStatus(500, "500 Internal Server Error")}}</dt>
- <dd>The server has encountered a situation it doesn't know how to handle.</dd>
- <dt>{{HTTPStatus(501, "501 Not Implemented")}}</dt>
- <dd>The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are <code>GET</code> and <code>HEAD</code>.</dd>
- <dt>{{HTTPStatus(502, "502 Bad Gateway")}}</dt>
- <dd>This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.</dd>
- <dt>{{HTTPStatus(503, "503 Service Unavailable")}}</dt>
- <dd>The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This responses should be used for temporary conditions and the <code>Retry-After:</code> HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.</dd>
- <dt>{{HTTPStatus(504, "504 Gateway Timeout")}}</dt>
- <dd>This error response is given when the server is acting as a gateway and cannot get a response in time.</dd>
- <dt>{{HTTPStatus(505, "505 HTTP Version Not Supported")}}</dt>
- <dd>The HTTP version used in the request is not supported by the server.</dd>
- <dt>{{HTTPStatus(506, "506 Variant Also Negotiates")}}</dt>
- <dd>The server has an internal configuration error: transparent content negotiation for the request results in a circular reference.</dd>
- <dt>{{HTTPStatus(507, "507 Insufficient Storage")}}</dt>
- <dd>The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.</dd>
- <dt>{{HTTPStatus(508, "508 Loop Detected")}} ({{Glossary("WebDAV")}})</dt>
- <dd>The server detected an infinite loop while processing the request.</dd>
- <dt>{{HTTPStatus(510, "510 Not Extended")}}</dt>
- <dd>Further extensions to the request are required for the server to fulfill it.</dd>
- <dt>{{HTTPStatus(511, "511 Network Authentication Required")}}</dt>
- <dd>The 511 status code indicates that the client needs to authenticate to gain network access.</dd>
-</dl>
-
-<h2 id="Bakınız">Bakınız</h2>
-
-<ul>
- <li><a href="https://en.wikipedia.org/wiki/List_of_HTTP_status_codes">List of HTTP status codes on Wikipedia</a></li>
- <li><a href="http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml">IANA official registry of HTTP status codes</a></li>
-</ul>