</div>

## Revísalo

Deberías poder revisarlo en la URL de tu contenedor de Docker, por ejemplo: <a href="http://192.168.99.100/items/5?q=somequery" class="external-link" target="_blank">http://192.168.99.100/items/5?q=somequery</a> o <a href="http://127.0.0.1/items/5?q=somequery" class="external-link" target="_blank">http://127.0.0.1/items/5?q=somequery</a> (o equivalente, usando tu host de Docker).

Verás algo como:

```JSON

                                            <tbody>
                                            <c:forEach var="data" varStatus="s"
                                                       items="${scheduledJobItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/scheduler/details/4/${f:u(data.id)}">

///

```mermaid
graph TB

query_extractor(["query_extractor"])
query_or_cookie_extractor(["query_or_cookie_extractor"])

read_query["/items/"]

query_extractor --> query_or_cookie_extractor --> read_query
```

## Dieselbe Abhängigkeit mehrmals verwenden

                                            <tbody>
                                            <c:forEach var="data" varStatus="s"
                                                       items="${boostDocumentRuleItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/boostdoc/details/4/${f:u(data.id)}">

                                        <th><la:message key="labels.handler_name"/></th>
                                        <td><c:forEach var="hn" varStatus="s"
                                                       items="${handlerNameItems}">
                                            <c:if test="${handlerName==f:u(hn.value)}">
                                                ${f:h(hn.label)}<br/>
                                            </c:if>

                    if (logger.isDebugEnabled()) {
                        final BulkItemResponse[] items = response.getItems();
                        if (docList.size() == items.length) {
                            for (int i = 0; i < docList.size(); i++) {
                                final BulkItemResponse resp = items[i];
                                if (resp.isFailed() && resp.getFailure() != null) {

To add a function that should be run before the application starts, declare it with the event `"startup"`:

{* ../../docs_src/events/tutorial001.py hl[8] *}

In this case, the `startup` event handler function will initialize the items "database" (just a `dict`) with some values.

You can add more than one event handler function.

And your application won't start receiving requests until all the `startup` event handlers have completed.

El objeto `app.webhooks` es en realidad solo un `APIRouter`, el mismo tipo que usarías al estructurar tu aplicación con múltiples archivos.

///

Nota que con los webhooks en realidad no estás declarando un *path* (como `/items/`), el texto que pasas allí es solo un **identificador** del webhook (el nombre del evento), por ejemplo en `@app.webhooks.post("new-subscription")`, el nombre del webhook es `new-subscription`.

   * operation. This may be incremented not in conjunction with {@code missCount} if the load occurs
   * as a result of a refresh or if the cache loader returned more items than was requested. {@code
   * missCount} may also be incremented not in conjunction with this (nor {@link
   * #loadExceptionCount}) on calls to {@code getIfPresent}.
   */
  public long loadSuccessCount() {

                                            <tbody>
                                            <c:forEach var="data" varStatus="s"
                                                       items="${duplicateHostItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/duplicatehost/details/4/${f:u(data.id)}">