diff --git a/de/guide/writing-middleware.md b/de/guide/writing-middleware.md
index f31fc383..b6fd011d 100644
--- a/de/guide/writing-middleware.md
+++ b/de/guide/writing-middleware.md
@@ -11,7 +11,7 @@ redirect_from: " "
Überblick
-_Middlewarefunktionen_ sind Funktionen, die Zugriff auf das [Anforderungsobjekt](/{{ page.lang }}/5x/api.html#req) (`req`), das [Antwortobjekt](/{{ page.lang }}/5x/api.html#res) (`res`) und die nächste Middlewarefunktion im Anforderung/Antwort-Zyklus der Anwendung haben. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
Über Middlewarefunktionen lassen sich die folgenden Tasks ausführen:
@@ -38,9 +38,9 @@ Das folgende Beispiel zeigt die Elemente eines Middlewarefunktionsaufrufs:
Callback-Argument zur Middlewarefunktion, die nach der geltenden Konvention als "next" bezeichnet wird.
-HTTP-
Antwortargument zur Middlewarefunktion, die nach der geltenden Konvention als "res" bezeichnet wird.
HTTP
response argument to the middleware function, called "res" by convention.
HTTP-
Anforderungsargument zur Middlewarefunktion, die nach der geltenden Konvention als "req" bezeichnet wird.
HTTP
request argument to the middleware function, called "req" by convention.
Overview
-Las funciones de _middleware_ son funciones que tienen acceso al [objeto de solicitud](/{{ page.lang }}/5x/api.html#req) (`req`), al [objeto de respuesta](/{{ page.lang }}/5x/api.html#res) (`res`) y a la siguiente función de middleware en el ciclo de solicitud/respuestas de la aplicación. La siguiente función de middleware se denota normalmente con una variable denominada `next`.
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. La siguiente función de middleware se denota normalmente con una variable denominada `next`.
Las funciones de middleware pueden realizar las siguientes tareas:
@@ -38,9 +38,9 @@ El siguiente ejemplo muestra los elementos de una llamada a función de middlewa
Argumento de devolución de llamada a la función de middleware, denominado "next" por convención.
-Argumento de
respuesta HTTP a la función de middleware, denominado "res" por convención.
HTTP
response argument to the middleware function, called "res" by convention.
Argumento de
solicitud HTTP a la función de middleware, denominado "req" por convención.
HTTP
request argument to the middleware function, called "req" by convention.
Présentation
-Les fonctions de _middleware_ sont des fonctions qui peuvent accéder à l'[objet Request](/{{ page.lang }}/5x/api.html#req) (`req`), l'[objet response](/{{ page.lang }}/5x/api.html#res) (`res`) et à la fonction middleware suivant dans le cycle demande-réponse de l'application. La fonction middleware suivant est couramment désignée par une variable nommée `next`.
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. La fonction middleware suivant est couramment désignée par une variable nommée `next`.
Les fonctions middleware effectuent les tâches suivantes :
@@ -38,9 +38,9 @@ L'exemple suivant montre les éléments d'un appel de fonction middleware:
Argument de rappel à la fonction middleware, appelée "next" par convention.
-Argument de
réponse HTTP à la fonction middleware, appelé "res" par convention.
HTTP
response argument to the middleware function, called "res" by convention.
Argument de
demande HTTP à la fonction middleware, appelé "req" par convention.
HTTP
request argument to the middleware function, called "req" by convention.
Panoramica
-Le funzioni _middleware_ sono funzioni con accesso all'[oggetto richiesta](/{{ page.lang }}/5x/api.html#req) (`req`), all'[oggetto risposta](/{{ page.lang }}/5x/api.html#res) (`res`) e alla successiva funzione middleware nel ciclo richiesta-risposta dell'applicazione. La successiva funzione middleware viene comunemente denotata da una variabile denominata `next`.
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. La successiva funzione middleware viene comunemente denotata da una variabile denominata `next`.
Le funzioni middleware possono eseguire le attività elencate di seguito:
@@ -38,9 +38,9 @@ I seguenti esempi mostrano gli elementi di una chiamata alla funzione middleware
Argomento di callback nella funzione middleware, denominata per convenzione "next".
-Argomento
risposta HTTP nella funzione middleware, denominato "res" per convenzione.
HTTP
response argument to the middleware function, called "res" by convention.
Argomento
richiesta HTTP nella funzione middleware, denominato "req" per convenzione.
HTTP
request argument to the middleware function, called "req" by convention.
概説
-_ミドルウェア_ 関数は、[リクエストオブジェクト](/{{ page.lang }}/5x/api.html#req) (`req`)、[レスポンスオブジェクト](/{{ page.lang }}/5x/api.html#res) (`res`)、およびアプリケーションのリクエストレスポンスサイクルにおける次のミドルウェア関数に対するアクセス権限を持つ関数です。次のミドルウェア関数は一般的に、`next` という変数で表されます。 The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
ミドルウェア関数は以下のタスクを実行できます。
@@ -38,9 +38,9 @@ _ミドルウェア_ 関数は、[リクエストオブジェクト](/{{ page.la
ミドルウェア関数へのコールバック引数 (慣習的に「next」と呼ばれます)。
-ミドルウェア関数への HTTP
レスポンス引数 (慣習的に「res」と呼ばれます)。
HTTP
response argument to the middleware function, called "res" by convention.
ミドルウェア関数への HTTP
リクエスト引数 (慣習的に「req」と呼ばれます)。
HTTP
request argument to the middleware function, called "req" by convention.
개요
-_미들웨어_ 함수는 [요청 오브젝트](/{{ page.lang }}/5x/api.html#req)(`req`), [응답 오브젝트](/{{ page.lang }}/5x/api.html#res) (`res`), 그리고 애플리케이션의 요청-응답 주기 중 그 다음의 미들웨어 함수 대한 액세스 권한을 갖는 함수입니다. 그 다음의 미들웨어 함수는 일반적으로 `next`라는 이름의 변수로 표시됩니다.
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. 그 다음의 미들웨어 함수는 일반적으로 `next`라는 이름의 변수로 표시됩니다.
미들웨어 함수는 다음과 같은 태스크를 수행할 수 있습니다.
@@ -38,9 +38,9 @@ _미들웨어_ 함수는 [요청 오브젝트](/{{ page.lang }}/5x/api.html#req)
미들웨어 함수에 대한 콜백 인수(일반적으로 "next"라 불림).
-미들웨어 함수에 대한 HTTP
응답 인수(일반적으로 "res"라 불림).
HTTP
response argument to the middleware function, called "res" by convention.
미들웨어 함수에 대한 HTTP
요청 인수(일반적으로 "req"라 불림).
HTTP
request argument to the middleware function, called "req" by convention.
Visão Geral
-Funções de _Middleware_ são funções que tem acesso
-ao [objeto de solicitação](/{{ page.lang }}/5x/api.html#req)
-(`req`), o [objeto de resposta](/{{ page.lang }}/5x/api.html#res)
-(`res`), e a próxima função de middleware no ciclo
-solicitação-resposta do aplicativo. A próxima função middleware é
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. A próxima função middleware é
comumente denotada por uma variável chamada `next`.
Funções de middleware podem executar as seguintes tarefas:
@@ -46,9 +42,9 @@ O exemplo a seguir mostra os elementos de uma chamada de função de middleware:
Argumento de retorno de chamada para a função de middleware, chamado de "next" por convenção.
-Argumento de
resposta HTTP para a função de middleware, chamado de "res" por convenção.
HTTP
response argument to the middleware function, called "res" by convention.
Argumento de
solicitação HTTP para a função de middleware, chamado de "req" por convenção.
HTTP
request argument to the middleware function, called "req" by convention.
概述
-_中间件_函数能够访问[请求对象](/{{ page.lang }}/5x/api.html#req) (`req`)、[响应对象](/{{ page.lang }}/5x/api.html#res) (`res`) 以及应用程序的请求/响应循环中的下一个中间件函数。下一个中间件函数通常由名为 `next` 的变量来表示。 The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
+_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
中间件函数可以执行以下任务：
@@ -38,9 +38,9 @@ _中间件_函数能够访问[请求对象](/{{ page.lang }}/5x/api.html#req) (`
中间件函数的回调自变量，按约定称为“next”。
-中间件函数的 HTTP
响应自变量，按约定称为“res”。
HTTP
response argument to the middleware function, called "res" by convention.
中间件函数的 HTTP
请求自变量，按约定称为“req”。
HTTP
request argument to the middleware function, called "req" by convention.
中介軟體函數的回呼引數，依慣例，稱為 "next"。
-
+HTTP
response argument to the middleware function, called "res" by convention.
中介軟體函數的 HTTP
request 引數，依慣例，稱為 "req"。
HTTP
request argument to the middleware function, called "req" by convention.