## Using the `jsonable_encoder` in a `Response` { #using-the-jsonable-encoder-in-a-response }

Because **FastAPI** doesn't make any changes to a `Response` you return, you have to make sure its contents are ready for it.

For example, you cannot put a Pydantic model in a `JSONResponse` without first converting it to a `dict` with all the data types (like `datetime`, `UUID`, etc) converted to JSON-compatible types.

        return 0;
    }

    @Override
    int readParametersWireFormat(final byte[] buffer, int bufferIndex, final int len) {
        available = readInt2(buffer, bufferIndex);
        bufferIndex += 2;
        int head = readInt2(buffer, bufferIndex);
        bufferIndex += 2;
        status = readInt2(buffer, bufferIndex);
        return 6;
    }

    @Override

	<scm>
		<connection>scm:git:******@****.***:codelibs/corelib.git</connection>
		<url>scm:git:******@****.***:codelibs/corelib.git</url>
		<developerConnection>scm:git:******@****.***:codelibs/corelib.git</developerConnection>
	  <tag>HEAD</tag>
  </scm>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	</properties>
	<build>
		<plugins>
			<plugin>
				<artifactId>maven-compiler-plugin</artifactId>

///

#### Opération

"Opération" fait référence à une des "méthodes" HTTP.

Une de :

* `POST`
* `GET`
* `PUT`
* `DELETE`

...ou une des plus exotiques :

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`

Dans le protocol HTTP, vous pouvez communiquer avec chaque chemin en utilisant une (ou plus) de ces "méthodes".

---

		<connection>scm:git:******@****.***:codelibs/fess-crawler.git</connection>
		<developerConnection>scm:git:******@****.***:codelibs/fess-crawler.git</developerConnection>
		<url>******@****.***:codelibs/fess-crawler.git</url>
	  <tag>HEAD</tag>
  </scm>
	<parent>
		<groupId>org.codelibs.fess</groupId>
		<artifactId>fess-parent</artifactId>
		<version>15.3.0-SNAPSHOT</version>
	</parent>
	<modules>
		<module>fess-crawler</module>

        }
    }

    @Test
    void causeConstructor_setsCause_andDerivesMessageFromCauseToString() {
        // Arrange - use a real cause so message is derived from cause.toString()
        Throwable cause = new IllegalStateException("proto mismatch");
        String expectedMessage = cause.toString();

        // Act

        }
    }

    @Test
    @DisplayName("customizeCreate sets required flags and extended mode")
    void customizeCreateSetsFlagsAndExtended() throws Exception {
        // Arrange: real instance to call protected method; collaborators mocked for interaction verification
        SmbNamedPipe pipe = new SmbNamedPipe("smb://server/IPC$/foo", SmbPipeResource.PIPE_TYPE_RDWR, ctx());

            "The TID specified was invalid.", "The handle is invalid.", "The network name cannot be found.",
            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",
            "The process cannot access the file because it is being used by another process.",

            "The TID specified was invalid.", "The handle is invalid.", "The network name cannot be found.",
            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",
            "The process cannot access the file because it is being used by another process.",

Status of delete marker replication can be viewed by doing a GET/HEAD on the object version - it will return a `X-Minio-Replication-DeleteMarker-Status` header and http response code of `405`. In the case of permanent deletes, if the delete replication is pending or failed to propagate to the target cluster, GET/HEAD will return additional `X-Minio-Replication-Delete-Status` header and a http response code of `405`.