Наприклад, якщо клієнт спробує надіслати query параметр `tool` зі значенням `plumbus`, як у цьому запиті:

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

Він отримає відповідь з **помилкою**, яка повідомить, що query параметр `tool ` не дозволено:

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

        - '!fastapi/**'
        - '!pyproject.toml'
        - '!docs/en/data/sponsors.yml'
        - '!docs/en/overrides/main.html'

lang-all:
  - all:
    - changed-files:
      - any-glob-to-any-file:
        - docs/*/docs/**
      - all-globs-to-all-files:
        - '!docs/en/docs/**'
        - '!docs/*/**/_*.md'
        - '!fastapi/**'
        - '!pyproject.toml'

internal:
  - all:
    - changed-files:

	}

	// Compute OR of conditions
	result := false
	for _, ex := range e.And {
		res, err := ex.evalNode(r, tableAlias)
		if err != nil {
			return nil, err
		}
		b, ok := res.ToBool()
		if !ok {
			return nil, errExpectedBool
		}
		if b {
			return FromBool(true), nil
		}
		result = result || b
	}
	return FromBool(result), nil
}

如果客户尝试发送一些**额外的 headers**，他们将收到**错误**响应。

例如，如果客户端尝试发送一个值为 `plumbus` 的 `tool` header，客户端将收到一个**错误**响应，告知他们 header 参数 `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.
 */

/**
 * Maven Upgrade Tool Goals and Strategies.
 *
 * <p>This package contains the implementation of the Maven upgrade tool (mvnup) that helps
 * upgrade Maven projects to be compatible with Maven 4. The tool is organized around
 * a goal-based architecture with pluggable upgrade strategies.</p>
 *
 * <h2>Architecture Overview</h2>
 *

* They are not synced with the code to reflect the eventual solution that is committed
* Google Docs is not a "code-oriented" tool, like Markdown can be
* Review in Google Docs is not as simple as a PR code review in GitHub

## Decision

The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow.

Por exemplo, se o cliente tentar enviar um parâmetro de consulta `tool` com o valor `plumbus`, como:

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

Eles receberão um retorno de **erro** informando-os que o parâmentro de consulta `tool` não é permitido:

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

    public static final String MVNENC_NAME = "Maven Password Encrypting Tool";

    public static final String MVNSHELL_CMD = "mvnsh";
    public static final String MVNSHELL_NAME = "Maven Shell Tool";

    public static final String MVNUP_CMD = "mvnup";
    public static final String MVNUP_NAME = "Maven Upgrade Tool";

# 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

Zum Beispiel, wenn der Client versucht, einen `tool`-Header mit einem Wert von `plumbus` zu senden, erhält er eine **Error-Response**, die ihm mitteilt, dass der Header-Parameter `tool` nicht erlaubt ist:

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