Imagine you develop an app that allows creating invoices.

These invoices will have an `id`, `title` (optional), `customer`, and `total`.

The user of your API (an external developer) will create an invoice in your API with a POST request.

Then your API will (let's imagine):

* Send the invoice to some customer of the external developer.
* Collect the money.
* Send a notification back to the API user (the external developer).

identifiable information (PII). When the same data is processed for analytics, PII should be redacted. However, if the same dataset is used for a marketing campaign, you might need to enrich the data with additional details, such as information from the customer loyalty database.

MinIO's Object Lambda, enables application developers to process data retrieved from MinIO before returning it to an application. You can register a Lambda Function target on MinIO, once successfully registered it can be...

// the handler should ensure to remove these keys before sending them to the object layer.
// Currently these keys are:
//   - X-Amz-Server-Side-Encryption-Customer-Key
//   - X-Amz-Copy-Source-Server-Side-Encryption-Customer-Key
func (api objectAPIHandlers) NewMultipartUploadHandler(w http.ResponseWriter, r *http.Request) {
	ctx := newContext(r, w, "NewMultipartUpload")

// the handler should ensure to remove these keys before sending them to the object layer.
// Currently these keys are:
//   - X-Amz-Server-Side-Encryption-Customer-Key
//   - X-Amz-Copy-Source-Server-Side-Encryption-Customer-Key
func (api objectAPIHandlers) CopyObjectHandler(w http.ResponseWriter, r *http.Request) {
	ctx := newContext(r, w, "CopyObject")

## Custom response class { #custom-response-class }

You can create your own custom response class, inheriting from `Response` and using it.

For example, let's say that you want to use <a href="https://github.com/ijl/orjson" class="external-link" target="_blank">`orjson`</a>, but with some custom settings not used in the included `ORJSONResponse` class.

* Automatically logging all request bodies.

## Handling custom request body encodings { #handling-custom-request-body-encodings }

Let's see how to make use of a custom `Request` subclass to decompress gzip requests.

And an `APIRoute` subclass to use that custom request class.

### Create a custom `GzipRequest` class { #create-a-custom-gziprequest-class }

/// tip

The same as when using a custom CDN, the first step is to disable the automatic docs, as those use the CDN by default.

To disable them, set their URLs to `None` when creating your `FastAPI` app:

{* ../../docs_src/custom_docs_ui/tutorial002.py hl[9] *}

### Include the custom docs for static files { #include-the-custom-docs-for-static-files }

            }
        };

        assertTrue(customEnv.is("bool.true"));
        assertFalse(customEnv.is("bool.false"));
        assertTrue(customEnv.is("bool.yes"));
        assertFalse(customEnv.is("bool.no"));
        assertTrue(customEnv.is("bool.on"));
        assertFalse(customEnv.is("bool.off"));
        assertTrue(customEnv.is("bool.1"));
        assertFalse(customEnv.is("bool.0"));
    }

            }
        };

        // Set the customizer
        pagerCreator.setPagerCustomizer(customizer);

        // Verify it can be retrieved
        assertSame(customizer, pagerCreator.getPagerCustomizer());
    }

    // Test multiple set operations
    public void test_setPagerCustomizer_multiple_times() {
        // Create first customizer
        ComponentCustomizer customizer1 = new ComponentCustomizer() {

            // Circuit should be OPEN after 3 failures
            assertEquals(State.OPEN, customCb.getState(), "Circuit should be OPEN after regular failures");
            assertEquals(3, customCb.getFailureCount(), "Should have 3 failures");

            // Reset for custom predicate test
            customCb.reset();
            assertEquals(State.CLOSED, customCb.getState(), "Circuit should be CLOSED after reset");