* The [Gradle Tooling API client](https://docs.gradle.org/8.8/userguide/third_party_integration.html#embedding)
  * This requires a Java application, and thus runtime, to run the tooling API client

As indicated, each of those components require a Java runtime to run.

The recommended way of invoking Gradle is to use the Gradle Wrapper.

                        "responses": {
                            "200": {
                                "description": "Successful Response",
                                "content": {
                                    "application/json": {
                                        "schema": {
                                            "$ref": "#/components/schemas/Model3"
                                        }
                                    }

                        "responses": {
                            "200": {
                                "description": "Successful Response",
                                "content": {"application/json": {"schema": {}}},
                            }
                        },
                    }
                }
            },
        }

* and don't send any authentication credentials.

This type of attack is mainly relevant when:

* the application is running locally (e.g. on `localhost`) or in an internal network
* and the application doesn't have any authentication, it expects that any request from the same network can be trusted.

## Example Attack { #example-attack }

                                "content": {"application/json": {"schema": {}}},
                            },
                            "422": {
                                "description": "Validation Error",
                                "content": {
                                    "application/json": {
                                        "schema": {

 * governing permissions and limitations under the License.
 */
package org.codelibs.fess.app.service;

/**
 * Abstract base class for Fess application services.
 * This class provides common functionality and utilities for service implementations
 * throughout the Fess search application.
 */
public abstract class FessAppService {

    /**
     * Default constructor.
     */
    public FessAppService() {

    Request request = new Request.Builder()
        .url("https://api.github.com/repos/square/okhttp/issues")
        .header("User-Agent", "OkHttp Headers.java")
        .addHeader("Accept", "application/json; q=0.5")
        .addHeader("Accept", "application/vnd.github.v3+json")
        .build();

    try (Response response = client.newCall(request).execute()) {
      if (!response.isSuccessful()) throw new IOException("Unexpected code " + response);

      """
      |--simple boundary
      |
      |abcd
      |--simple boundary--
      """.trimMargin()
        .replace("\n", "\r\n")

    val responseBody =
      multipart.toResponseBody(
        "application/multipart; boundary=\"simple boundary\"".toMediaType(),
      )

    val parts = MultipartReader(responseBody)
    assertThat(parts.boundary).isEqualTo("simple boundary")

    val part = parts.nextPart()!!

        responseData.setUrl("http://example.com/document.pdf");
        assertEquals("http://example.com/document.pdf", responseData.getUrl());

        responseData.setMimeType("application/pdf");
        assertEquals("application/pdf", responseData.getMimeType());

        responseData.setCharSet("UTF-8");
        assertEquals("UTF-8", responseData.getCharSet());

        responseData.setHttpStatusCode(200);

## JSON Lines { #json-lines }

En estos casos, es común enviar "**JSON Lines**", que es un formato donde envías un objeto JSON por línea.

Una response tendría un tipo de contenido `application/jsonl` (en lugar de `application/json`) y el response body sería algo como:

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}
{"name": "Portal Gun", "description": "A portal opening device."}