{* ../../docs_src/request_form_models/tutorial002_an_py39.py hl[12] *}

If a client tries to send some extra data, they will receive an **error** response.

For example, if the client tries to send the form fields:

* `username`: `Rick`
* `password`: `Portal Gun`
* `extra`: `Mr. Poopybutthole`

They will receive an error response telling them that the field `extra` is not allowed:

```json
{
    "detail": [
        {

            RdmaMemoryRegion recvRegion = bufferManager.getReceiveRegion();
            assertNotNull(recvRegion, "Receive region should not be null");
            assertTrue(recvRegion.getSize() > 0, "Receive region should have positive size");
            assertNotNull(recvRegion.getBuffer(), "Receive region buffer should not be null");

            // Test buffer pooling statistics

If a client tries to send some **extra cookies**, they will receive an **error** response.

Poor cookie banners with all their effort to get your consent for the <abbr title="This is another joke. Don't pay attention to me. Have some coffee for your cookie. ☕">API to reject it</abbr>. 🍪

For example, it doesn't receive `datetime` objects, as those are not compatible with JSON.

So, a `datetime` object would have to be converted to a `str` containing the data in <a href="https://en.wikipedia.org/wiki/ISO_8601" class="external-link" target="_blank">ISO format</a>.

The same way, this database wouldn't receive a Pydantic model (an object with attributes), only a `dict`.

In your WebSocket route you can `await` for messages and send messages.

{* ../../docs_src/websockets/tutorial001_py39.py hl[48:52] *}

You can receive and send binary, text, and JSON data.

## Try it { #try-it }

If your file is named `main.py`, run your application with:

<div class="termy">

```console
$ fastapi dev main.py

     * @throws CIFSException if an error occurs retrieving the buffer size
     */
    int getSendBufferSize() throws CIFSException;

    /**
     * Gets the receive buffer size of the underlying SMB connection
     * @return the receive buffer size of the underlying connection
     * @throws CIFSException if an error occurs retrieving the buffer size
     */
    int getReceiveBufferSize() throws CIFSException;

    /**

        assertEquals(1, cleaned);
        assertNull(leaseManager.getLease(key));
    }

    @Test
    @DisplayName("Should not clean up recent leases")
    void testCleanupRecentLeases() {
        String path = "/share/recent.txt";
        int requestedState = Smb2LeaseState.SMB2_LEASE_READ_CACHING;

        Smb2LeaseKey key = leaseManager.requestLease(path, requestedState);

{* ../../docs_src/body_updates/tutorial001_py310.py hl[28:33] *}

`PUT` is used to receive data that should replace the existing data.

### Warning about replacing { #warning-about-replacing }

That means that if you want to update the item `bar` using `PUT` with a body containing:

```Python
{

        assertNotNull(capabilities, "Capabilities should not be null");
        assertEquals(1, capabilities.size(), "TCP provider should only support send/receive");
        assertTrue(capabilities.contains(RdmaCapability.RDMA_SEND_RECEIVE), "Should support send/receive");
        assertFalse(capabilities.contains(RdmaCapability.RDMA_READ), "Should not support RDMA read");

If the client requests `http://example.com/items/foo` (an `item_id` `"foo"`), that client will receive an HTTP status code of 200, and a JSON response of:

```JSON
{
  "item": "The Foo Wrestlers"
}
```

But if the client requests `http://example.com/items/bar` (a non-existent `item_id` `"bar"`), that client will receive an HTTP status code of 404 (the "not found" error), and a JSON response of:

```JSON
{