Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions de/guide/writing-middleware.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ redirect_from: " "

<h2>Überblick</h2>

_Middlewarefunktionen_ sind Funktionen, die Zugriff auf das [Anforderungsobjekt](/{{ page.lang }}/4x/api.html#req) (`req`), das [Antwortobjekt](/{{ page.lang }}/4x/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.
_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.

Über Middlewarefunktionen lassen sich die folgenden Tasks ausführen:

Expand All @@ -38,9 +38,9 @@ Das folgende Beispiel zeigt die Elemente eines Middlewarefunktionsaufrufs:

<div class="callout" id="callout4">Callback-Argument zur Middlewarefunktion, die nach der geltenden Konvention als "next" bezeichnet wird.</div>

<div class="callout" id="callout5">HTTP-<a href="../4x/api.html#res">Antwort</a>argument zur Middlewarefunktion, die nach der geltenden Konvention als "res" bezeichnet wird.</div>
<div class="callout" id="callout5">HTTP-<a href="../5x/api.html#res">Antwort</a>argument zur Middlewarefunktion, die nach der geltenden Konvention als "res" bezeichnet wird.</div>

<div class="callout" id="callout6">HTTP-<a href="../4x/api.html#req">Anforderungs</a>argument zur Middlewarefunktion, die nach der geltenden Konvention als "req" bezeichnet wird.</div>
<div class="callout" id="callout6">HTTP-<a href="../5x/api.html#req">Anforderungs</a>argument zur Middlewarefunktion, die nach der geltenden Konvention als "req" bezeichnet wird.</div>
</td></tr>
</table>
</div>
Expand Down
6 changes: 3 additions & 3 deletions en/guide/writing-middleware.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ redirect_from: "/guide/writing-middleware.html"

<h2>Overview</h2>

_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/4x/api.html#req) (`req`), the [response object](/{{ page.lang }}/4x/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.
_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.

Middleware functions can perform the following tasks:

Expand All @@ -38,9 +38,9 @@ The following figure shows the elements of a middleware function call:

<div class="callout" id="callout4">Callback argument to the middleware function, called "next" by convention.</div>

<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/4x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>

<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/4x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
</td></tr>
</table>
</div>
Expand Down
6 changes: 3 additions & 3 deletions es/guide/writing-middleware.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ redirect_from: " "

<h2>Overview</h2>

Las funciones de _middleware_ son funciones que tienen acceso al [objeto de solicitud](/{{ page.lang }}/4x/api.html#req) (`req`), al [objeto de respuesta](/{{ page.lang }}/4x/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`.
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`.

Las funciones de middleware pueden realizar las siguientes tareas:

Expand All @@ -38,9 +38,9 @@ El siguiente ejemplo muestra los elementos de una llamada a función de middlewa

<div class="callout" id="callout4">Argumento de devolución de llamada a la función de middleware, denominado "next" por convención.</div>

<div class="callout" id="callout5">Argumento de <a href="../4x/api.html#res">respuesta</a> HTTP a la función de middleware, denominado "res" por convención.</div>
<div class="callout" id="callout5">Argumento de <a href="../5x/api.html#res">respuesta</a> HTTP a la función de middleware, denominado "res" por convención.</div>

<div class="callout" id="callout6">Argumento de <a href="../4x/api.html#req">solicitud</a> HTTP a la función de middleware, denominado "req" por convención.</div>
<div class="callout" id="callout6">Argumento de <a href="../5x/api.html#req">solicitud</a> HTTP a la función de middleware, denominado "req" por convención.</div>
</td></tr>
</table>
</div>
Expand Down
6 changes: 3 additions & 3 deletions fr/guide/writing-middleware.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ redirect_from: " "

<h2>Présentation</h2>

Les fonctions de _middleware_ sont des fonctions qui peuvent accéder à l'[objet Request](/{{ page.lang }}/4x/api.html#req) (`req`), l'[objet response](/{{ page.lang }}/4x/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`.
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`.

Les fonctions middleware effectuent les tâches suivantes :

Expand All @@ -38,9 +38,9 @@ L'exemple suivant montre les éléments d'un appel de fonction middleware:

<div class="callout" id="callout4">Argument de rappel à la fonction middleware, appelée "next" par convention.</div>

<div class="callout" id="callout5">Argument de <a href="../4x/api.html#res">réponse</a> HTTP à la fonction middleware, appelé "res" par convention.</div>
<div class="callout" id="callout5">Argument de <a href="../5x/api.html#res">réponse</a> HTTP à la fonction middleware, appelé "res" par convention.</div>

<div class="callout" id="callout6">Argument de <a href="../4x/api.html#req">demande</a> HTTP à la fonction middleware, appelé "req" par convention.</div>
<div class="callout" id="callout6">Argument de <a href="../5x/api.html#req">demande</a> HTTP à la fonction middleware, appelé "req" par convention.</div>
</td></tr>
</table>
</div>
Expand Down
6 changes: 3 additions & 3 deletions it/guide/writing-middleware.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ redirect_from: " "

<h2>Panoramica</h2>

Le funzioni _middleware_ sono funzioni con accesso all'[oggetto richiesta](/{{ page.lang }}/4x/api.html#req) (`req`), all'[oggetto risposta](/{{ page.lang }}/4x/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`.
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`.

Le funzioni middleware possono eseguire le attività elencate di seguito:

Expand All @@ -38,9 +38,9 @@ I seguenti esempi mostrano gli elementi di una chiamata alla funzione middleware

<div class="callout" id="callout4">Argomento di callback nella funzione middleware, denominata per convenzione "next".</div>

<div class="callout" id="callout5">Argomento <a href="../4x/api.html#res">risposta</a> HTTP nella funzione middleware, denominato "res" per convenzione.</div>
<div class="callout" id="callout5">Argomento <a href="../5x/api.html#res">risposta</a> HTTP nella funzione middleware, denominato "res" per convenzione.</div>

<div class="callout" id="callout6">Argomento <a href="../4x/api.html#req">richiesta</a> HTTP nella funzione middleware, denominato "req" per convenzione.</div>
<div class="callout" id="callout6">Argomento <a href="../5x/api.html#req">richiesta</a> HTTP nella funzione middleware, denominato "req" per convenzione.</div>
</td></tr>
</table>
</div>
Expand Down
6 changes: 3 additions & 3 deletions ja/guide/writing-middleware.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ redirect_from: " "

<h2>概説</h2>

_ミドルウェア_ 関数は、[リクエストオブジェクト](/{{ page.lang }}/4x/api.html#req) (`req`)、[レスポンスオブジェクト](/{{ page.lang }}/4x/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.
_ミドルウェア_ 関数は、[リクエストオブジェクト](/{{ 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.

ミドルウェア関数は以下のタスクを実行できます。

Expand All @@ -38,9 +38,9 @@ _ミドルウェア_ 関数は、[リクエストオブジェクト](/{{ page.la

<div class="callout" id="callout4">ミドルウェア関数へのコールバック引数 (慣習的に「next」と呼ばれます)。</div>

<div class="callout" id="callout5">ミドルウェア関数への HTTP <a href="../4x/api.html#res">レスポンス</a>引数 (慣習的に「res」と呼ばれます)。</div>
<div class="callout" id="callout5">ミドルウェア関数への HTTP <a href="../5x/api.html#res">レスポンス</a>引数 (慣習的に「res」と呼ばれます)。</div>

<div class="callout" id="callout6">ミドルウェア関数への HTTP <a href="../4x/api.html#req">リクエスト</a>引数 (慣習的に「req」と呼ばれます)。</div>
<div class="callout" id="callout6">ミドルウェア関数への HTTP <a href="../5x/api.html#req">リクエスト</a>引数 (慣習的に「req」と呼ばれます)。</div>
</td></tr>
</table>
</div>
Expand Down
6 changes: 3 additions & 3 deletions ko/guide/writing-middleware.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ redirect_from: " "

<h2>개요</h2>

_미들웨어_ 함수는 [요청 오브젝트](/{{ page.lang }}/4x/api.html#req)(`req`), [응답 오브젝트](/{{ page.lang }}/4x/api.html#res) (`res`), 그리고 애플리케이션의 요청-응답 주기 중 그 다음의 미들웨어 함수 대한 액세스 권한을 갖는 함수입니다. 그 다음의 미들웨어 함수는 일반적으로 `next`라는 이름의 변수로 표시됩니다.
_미들웨어_ 함수는 [요청 오브젝트](/{{ page.lang }}/5x/api.html#req)(`req`), [응답 오브젝트](/{{ page.lang }}/5x/api.html#res) (`res`), 그리고 애플리케이션의 요청-응답 주기 중 그 다음의 미들웨어 함수 대한 액세스 권한을 갖는 함수입니다. 그 다음의 미들웨어 함수는 일반적으로 `next`라는 이름의 변수로 표시됩니다.

미들웨어 함수는 다음과 같은 태스크를 수행할 수 있습니다.

Expand All @@ -38,9 +38,9 @@ _미들웨어_ 함수는 [요청 오브젝트](/{{ page.lang }}/4x/api.html#req)

<div class="callout" id="callout4">미들웨어 함수에 대한 콜백 인수(일반적으로 "next"라 불림).</div>

<div class="callout" id="callout5">미들웨어 함수에 대한 HTTP <a href="../4x/api.html#res">응답</a> 인수(일반적으로 "res"라 불림).</div>
<div class="callout" id="callout5">미들웨어 함수에 대한 HTTP <a href="../5x/api.html#res">응답</a> 인수(일반적으로 "res"라 불림).</div>

<div class="callout" id="callout6">미들웨어 함수에 대한 HTTP <a href="../4x/api.html#req">요청</a> 인수(일반적으로 "req"라 불림).</div>
<div class="callout" id="callout6">미들웨어 함수에 대한 HTTP <a href="../5x/api.html#req">요청</a> 인수(일반적으로 "req"라 불림).</div>
</td></tr>
</table>
</div>
Expand Down
8 changes: 4 additions & 4 deletions pt-br/guide/writing-middleware.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@ redirect_from: " "
<h2>Visão Geral</h2>

Funções de _Middleware_ são funções que tem acesso
ao [objeto de solicitação](/{{ page.lang }}/4x/api.html#req)
(`req`), o [objeto de resposta](/{{ page.lang }}/4x/api.html#res)
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 é
comumente denotada por uma variável chamada `next`.
Expand Down Expand Up @@ -46,9 +46,9 @@ O exemplo a seguir mostra os elementos de uma chamada de função de middleware:

<div class="callout" id="callout4">Argumento de retorno de chamada para a função de middleware, chamado de "next" por convenção.</div>

<div class="callout" id="callout5">Argumento de <a href="../4x/api.html#res">resposta</a> HTTP para a função de middleware, chamado de "res" por convenção.</div>
<div class="callout" id="callout5">Argumento de <a href="../5x/api.html#res">resposta</a> HTTP para a função de middleware, chamado de "res" por convenção.</div>

<div class="callout" id="callout6">Argumento de <a href="../4x/api.html#req">solicitação</a> HTTP para a função de middleware, chamado de "req" por convenção.</div>
<div class="callout" id="callout6">Argumento de <a href="../5x/api.html#req">solicitação</a> HTTP para a função de middleware, chamado de "req" por convenção.</div>
</td></tr>
</table>
</div>
Expand Down
6 changes: 3 additions & 3 deletions zh-cn/guide/writing-middleware.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ redirect_from: " "

<h2>概述</h2>

_中间件_函数能够访问[请求对象](/{{ page.lang }}/4x/api.html#req) (`req`)、[响应对象](/{{ page.lang }}/4x/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.
_中间件_函数能够访问[请求对象](/{{ 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.

中间件函数可以执行以下任务:

Expand All @@ -38,9 +38,9 @@ _中间件_函数能够访问[请求对象](/{{ page.lang }}/4x/api.html#req) (`

<div class="callout" id="callout4">中间件函数的回调自变量,按约定称为“next”。</div>

<div class="callout" id="callout5">中间件函数的 HTTP <a href="../4x/api.html#res">响应</a>自变量,按约定称为“res”。</div>
<div class="callout" id="callout5">中间件函数的 HTTP <a href="../5x/api.html#res">响应</a>自变量,按约定称为“res”。</div>

<div class="callout" id="callout6">中间件函数的 HTTP <a href="../4x/api.html#req">请求</a>自变量,按约定称为“req”。</div>
<div class="callout" id="callout6">中间件函数的 HTTP <a href="../5x/api.html#req">请求</a>自变量,按约定称为“req”。</div>
</td></tr>
</table>
</div>
Expand Down
6 changes: 3 additions & 3 deletions zh-tw/guide/writing-middleware.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ redirect_from: " "

<h2>概觀</h2>

_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/4x/api.html#req) (`req`), the [response object](/{{ page.lang }}/4x/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.
_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.

Middleware functions can perform the following tasks:

Expand All @@ -38,9 +38,9 @@ The following figure shows the elements of a middleware function call:

<div class="callout" id="callout4">中介軟體函數的回呼引數,依慣例,稱為 "next"。</div>

<div class="callout" id="callout5">中介軟體函數的 HTTP <a href="../4x/api.html#res">response</a> 引數,依慣例,稱為 "res"。</div>
<div class="callout" id="callout5">中介軟體函數的 HTTP <a href="../5x/api.html#res">response</a> 引數,依慣例,稱為 "res"。</div>

<div class="callout" id="callout6">中介軟體函數的 HTTP <a href="../4x/api.html#req">request</a> 引數,依慣例,稱為 "req"。</div>
<div class="callout" id="callout6">中介軟體函數的 HTTP <a href="../5x/api.html#req">request</a> 引數,依慣例,稱為 "req"。</div>
</td></tr>
</table>
</div>
Expand Down