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

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

# when using variables like `TFCI_OUTPUT_DIR` in `docker exec commands,
# requiring conditional path adjustments throughout the CI scripts.
# Note: This does not work for `docker cp` commands.
# For a little more detail, see:
# https://github.com/tensorflow/tensorflow/blob/cc3006af6fea8d2a1360b3b5e65f9d14bbdb7094/ci/devinfra/docker/windows2022/Dockerfile#L196
TFCI_OUTPUT_WIN_DOCKER_DIR='C:/drive_t'

    /** The key of the message: Log Details */
    public static final String LABELS_searchlog_configuration_details = "{labels.searchlog_configuration_details}";

    /** The key of the message: Search Log */
    public static final String LABELS_searchlog_configuration_link_top = "{labels.searchlog_configuration_link_top}";

    /** The key of the message: Details */

                                                <tr
                                                        data-href="${contextPath}/admin/crawlinginfo/details/4/${f:u(data.id)}">
                                                    <td>${f:h(data.sessionId)}</td>
                                                    <td><fmt:formatDate

                                                <tr
                                                        data-href="${contextPath}/admin/dict/mapping/details/${f:u(dictId)}/4/${f:u(data.id)}">
                                                    <td>${f:h(data.inputs)}</td>
                                                    <td>${f:h(data.output)}</td>

                                                <tr
                                                        data-href="${contextPath}/admin/dict/stopwords/details/${f:u(dictId)}/4/${f:u(data.id)}">
                                                    <td>${f:h(data.inputValue)}</td>
                                                </tr>
                                            </c:forEach>

 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 * Lesser General Public License for more details.
 *
 * You should have received a copy of the GNU Lesser General Public
 * License along with this library; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */

You can combine `dataclasses` with other type annotations in many different combinations to form complex data structures.

Check the in-code annotation tips above to see more specific details.

## Learn More { #learn-more }

You can also combine `dataclasses` with other Pydantic models, inherit from them, include them in your own models, etc.

## Integrated middlewares { #integrated-middlewares }

**FastAPI** includes several middlewares for common use cases, we'll see next how to use them.

/// note | Technical Details

For the next examples, you could also use `from starlette.middleware.something import SomethingMiddleware`.

<img src="/img/tutorial/response-status-code/image02.png">

/// note | Technische Details

Sie können auch `from starlette import status` verwenden.

**FastAPI** bietet dieselben `starlette.status`-Codes auch via `fastapi.status` an, als Annehmlichkeit für Sie, den Entwickler. Sie kommen aber direkt von Starlette.