Ou você pode ter qualquer outra forma de comunicar com o endpoint WebSocket.

---

Mas para este exemplo, usaremos um documento HTML muito simples com algum JavaScript, tudo dentro de uma string longa.

Esse, é claro, não é o ideal e você não o usaria para produção.

Na produção, você teria uma das opções acima.

Либо вы можете сделать какой-либо другой способ взаимодействия с веб-сокетами.

---

Но для этого примера мы воспользуемся очень простым HTML документом с небольшими вставками JavaScript кода.

Конечно же это неоптимально, и на практике так делать не стоит.

В реальных приложениях стоит воспользоваться одним из вышеупомянутых способов.

   * <a href="http://www.rfc-editor.org/rfc/rfc4329.txt">RFC 4329</a> declares {@link
   * #JAVASCRIPT_UTF_8 application/javascript} to be the correct media type for JavaScript, but this
   * may be necessary in certain situations for compatibility.
   */
  public static final MediaType TEXT_JAVASCRIPT_UTF_8 = createConstantUtf8(TEXT_TYPE, "javascript");

  /**
   * <a href="http://www.iana.org/assignments/media-types/text/tab-separated-values">Tab separated

Or you might have any other way to communicate with the WebSocket endpoint.

---

But for this example, we'll use a very simple HTML document with some JavaScript, all inside a long string.

This, of course, is not optimal and you wouldn't use it for production.

In production you would have one of the options above.

</div>
<jsp:include page="/WEB-INF/view/common/admin/foot.jsp"></jsp:include>
<script src="${fe:url('/js/admin/plugins/form-validator/jquery.form-validator.min.js')}"
        type="text/javascript"></script>
<script src="${fe:url('/js/admin/searchlist.js')}" type="text/javascript"></script>
</body>

ftps:/example.com/  s:ftps p:/example.com/
gopher:/example.com/  s:gopher h:example.com p:/
ws:/example.com/  s:ws h:example.com p:/
wss:/example.com/  s:wss h:example.com p:/
data:/example.com/  s:data p:/example.com/
javascript:/example.com/  s:javascript p:/example.com/
mailto:/example.com/  s:mailto p:/example.com/
http:example.com/  s:http h:example.org p:/foo/example.com/
ftp:example.com/  s:ftp h:example.com p:/

*   [Go license example](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/go/operation.go#L1)
*   [Bash license example](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/ci_build/ci_build.sh#L2)
*   [JavaScript/TypeScript license example](https://github.com/tensorflow/tensorboard/blob/master/tensorboard/components/tf_backend/backend.ts#L1)

Bazel BUILD files also need to include a license section, e.g.,

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.

        }

        @ParameterizedTest
        @DisplayName("Should return correct mime type for multiple extensions")
        @CsvSource({ "txt, text/plain", "css, text/css", "js, application/x-javascript", "zip, application/zip", "tar, application/x-tar",
                "gz, application/x-gzip", "tiff, image/tiff", "tif, image/tiff" })
        void testVariousExtensions(String extension, String expectedMimeType) throws IOException {