---
title: "Integrate custom proxy"
slug: "integrate-custom-proxy"
abstract: ""
---
# Integrate custom proxy

To integrate a custom proxy in the Content SDK, extend the `ProxyHandler` class to create your own proxy implementation.

To integrate custom proxy:

1. Create a custom proxy class by extending the `ProxyHandler` class.

    > [!note]
    > If you need to inherit the default Sitecore methods, you can instead extend the `ProxyBase` class. In this case, your custom proxy must accept a `ProxyBaseConfig` argument in its constructor.

2. Implement the `handle` method to process requests.
3. Instantiate the proxy.
4. Pass the proxy instance to `defineProxy` in the Next.js proxy function definition.

## Example integration

The following example demonstrates how to seamlessly integrate a simple custom proxy that logs a request URL:

```ts
import { ProxyHandler } from '@sitecore-content-sdk/nextjs/proxy';
import { NextRequest, NextResponse } from 'next/server';

...

class LoggerProxy extends ProxyHandler {
  async handle(req: NextRequest, res: NextResponse): Promise<NextResponse> {
   console.log(`[LOGGER] ${req.method} ${req.url}`);
   return res || NextResponse.next();
  }
}
```

In the `proxy.ts` file, instantiate the custom proxy and add it to the proxy chain:

```csharp
export function proxy(req: NextRequest, event: NextFetchEvent) {

  ...
  const logger = new LoggerProxy();
  return defineProxy(logger, multisite, redirects, personalize).exec(req);
}
```

> [!note]
> There's no official method or helper to identify whether you're in the Editing mode inside your middleware. As a workaround, you can use the following Sitecore cookies to check whether you're in the Editing mode in your middleware:
>
> -   `sc_headless_mode`
>
> -   `sitename#sc_mode`
>
>
> Next.js also provides the `__next_preview_data` and `__prerender_bypass` cookies to enable [Preview Mode](http://nextjs.org/docs/pages/guides/preview-mode) (Pages Router) or [Draft Mode](https://nextjs.org/docs/app/guides/draft-mode) (App Router).