Use client tools like `mc` to set and listen for event notifications using the [`event` sub-command](https://docs.min.io/community/minio-object-store/reference/minio-mc/mc-event-add.html). MinIO SDK's [`BucketNotification` APIs](https://docs.min.io/community/minio-object-store/developers/go/API.html#setbucketnotification-ctx-context-context-bucketname-string-config-notification-configuration-error) can also be used. The notification message MinIO sends to publish an event is a JSON message...

- [Casdoor MinIO Integration](https://casdoor.org/docs/integration/minio)
- [MinIO STS Quickstart Guide](https://docs.min.io/community/minio-object-store/developers/security-token-service.html)

    //                                                                      ==============

    /**
     * Displays the main maintenance page.
     *
     * @return HTML response for the maintenance index page
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })
    public HtmlResponse index() {
        saveToken();
        return asIndexHtml();
    }

<%@page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8"%>
<ol class="breadcrumb float-sm-right">
	<c:if test="${crudMode == null}">
		<li class="breadcrumb-item active"><la:message key="labels.crud_link_list" /></li>
	</c:if>
	<c:if test="${crudMode != null}">
		<li class="breadcrumb-item"><la:link href="../list">
				<la:message key="labels.crud_link_list" />
			</la:link></li>
	</c:if>
	<c:if test="${crudMode == 1}">

<%@page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8"%>
<footer role="contentinfo">
	<div class="container text-center">
		<p class="text-muted">
			<la:message key="labels.footer.copyright" />
		</p>
	</div>

O podrías tener alguna otra forma de comunicarte con el endpoint de WebSocket.

---

Pero para este ejemplo, usaremos un documento HTML muy simple con algo de JavaScript, todo dentro de un string largo.

Esto, por supuesto, no es lo ideal y no lo usarías para producción.

En producción tendrías una de las opciones anteriores.

Oder Sie haben andere Möglichkeiten, mit dem WebSocket-Endpunkt zu kommunizieren.

---

Für dieses Beispiel verwenden wir jedoch ein sehr einfaches HTML-Dokument mit etwas JavaScript, alles in einem langen String.

Das ist natürlich nicht optimal und man würde das nicht in der Produktion machen.

In der Produktion hätten Sie eine der oben genannten Optionen.

<%@page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8"%>
<script src="${fe:url('/js/admin/jquery-3.7.1.min.js')}" type="text/javascript"></script>
<script src="${fe:url('/js/admin/popper.min.js')}" type="text/javascript"></script>
<script src="${fe:url('/js/admin/bootstrap.min.js')}" type="text/javascript"></script>
<script src="${fe:url('/js/admin/moment-with-locales.min.js')}" type="text/javascript"></script>

<%@page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8"%>
<c:if test="${crudMode == 1}">
	<button type="submit" class="btn btn-default" name="list"
		value="<la:message key="labels.crud_button_back" />">
		<em class="fa fa-arrow-circle-left">
		<la:message key="labels.crud_button_back" />
	</button>
	<c:if test="${editable}">
	<button type="submit" class="btn btn-success" name="create"
		value="<la:message key="labels.crud_button_create" />">

 * database to hold accepted cookies. The [cookie storage model][rfc_6265_53] specifies policies for
 * updating and expiring cookies.
 *
 * [rfc_6265_53]: https://tools.ietf.org/html/rfc6265#section-5.3
 */
interface CookieJar {
  /**
   * Saves [cookies] from an HTTP response to this store according to this jar's policy.
   *