Например, если клиент попытается отправить заголовок `tool` со значением `plumbus`, то в ответ он получит ошибку, сообщающую ему, что header-параметр `tool` не разрешен:

```json
{
    "detail": [
        {
            "type": "extra_forbidden",
            "loc": ["header", "tool"],
            "msg": "Extra inputs are not permitted",
            "input": "plumbus",
        }
    ]

// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

// Addr2line is a minimal simulation of the GNU addr2line tool,
// just enough to support pprof.
//
// Usage:
//
//	go tool addr2line binary
//
// Addr2line reads hexadecimal addresses, one per line and with optional 0x prefix,
// from standard input. For each input address, addr2line prints two output lines,

如果客戶端嘗試在**查詢參數**中發送一些**額外的**資料，他們將會收到一個**錯誤**回應。

例如，如果客戶端嘗試發送一個值為 `plumbus` 的 `tool` 查詢參數，如：

```http
https://example.com/items/?limit=10&tool=plumbus
```

他們將收到一個**錯誤**回應，告訴他們查詢參數 `tool` 是不允許的：

```json
{
    "detail": [
        {
            "type": "extra_forbidden",
            "loc": ["query", "tool"],
            "msg": "Extra inputs are not permitted",
            "input": "plumbus"
        }

# Use of this source code is governed by a BSD-style
# license that can be found in the LICENSE file.

eval `{go tool dist env -9}

if(! test -x $GOTOOLDIR/dist){
	echo 'cannot find $GOTOOLDIR/dist; nothing to clean' >[1=2]
	exit noclean
}

$GOBIN/go clean -i std
$GOBIN/go tool dist clean

예를 들어, 아래와 같이 만약 클라이언트가 `tool` 쿼리 매개변수에 `plumbus` 라는 값을 추가해서 보내려고 하면,

```http
https://example.com/items/?limit=10&tool=plumbus
```

클라이언트는 쿼리 매개변수 `tool` 이 허용되지 않는다는 **에러** 응답을 받게 됩니다.

```json
{
    "detail": [
        {
            "type": "extra_forbidden",
            "loc": ["query", "tool"],
            "msg": "Extra inputs are not permitted",

Наприклад, якщо клієнт спробує надіслати заголовок `tool` зі значенням `plumbus`, він отримає  **помилку** з повідомленням про те, що параметр заголовка `tool` не дозволений:

```json
{
    "detail": [
        {
            "type": "extra_forbidden",
            "loc": ["header", "tool"],
            "msg": "Extra inputs are not permitted",
            "input": "plumbus",
        }

 * specific language governing permissions and limitations
 * under the License.
 */

/**
 * Provides the API for the Maven Password Encryption tool ({@code mvnenc}).
 *
 * <p>This package contains interfaces and classes for the password encryption tool,
 * which helps secure sensitive information in Maven settings and configuration files.</p>
 *
 * <p>Key features include:</p>
 * <ul>

 * specific language governing permissions and limitations
 * under the License.
 */

/**
 * Provides the API for the Maven Upgrade tool ({@code mvnup}).
 *
 * <p>This package contains interfaces and classes for the Maven upgrade tool,
 * which provides functionality for upgrading Maven projects and dependencies.</p>
 *
 * <p>Key features include:</p>
 * <ul>
 *   <li>Project upgrade capabilities</li>

When you check the benchmarks, it is common to see several tools of different types compared as equivalent.

Specifically, to see Uvicorn, Starlette and FastAPI compared together (among many other tools).

The simpler the problem solved by the tool, the better performance it will get. And most of the benchmarks don't test the additional features provided by the tool.

The hierarchy is like:

* **Uvicorn**: an ASGI server

もしクライアントが**クエリパラメータ**として**余分な**データを送ろうとすると、**エラー**レスポンスが返されます。

例えば、クライアントがクエリパラメータ `tool` に、値 `plumbus` を設定して送ろうとすると:

```http
https://example.com/items/?limit=10&tool=plumbus
```

クエリパラメータ `tool` が許可されていないことを通知する**エラー**レスポンスが返されます。

```json
{
    "detail": [
        {
            "type": "extra_forbidden",
            "loc": ["query", "tool"],
            "msg": "Extra inputs are not permitted",