Document updated on Oct 2, 2026

Handling Client Redirects

When a backend returns a redirect, the default behavior of KrakenD is to follow the redirection and serve the final content to the user. When you don’t want this behavior and let the end client follow the redirect, you must enable the no_redirect HTTP client option.

No redirect configuration

The no_redirect option is one in the list of HTTP client options in the backend.

By enabling the flag, you can stop KrakenD from following redirections like a 301.

Example of configuration:

{
    "version": 4,
    "endpoints": [
        {
            "endpoint": "/redirect",
            "output_encoding": "no-op",
            "backend": [
                {
                    "url_pattern": "/__debug",
                    "encoding": "no-op",
                    "extra_config": {
                        "backend/http/client": {
                            "no_redirect": true
                        }
                    }
                }
            ]
        }
    ]
}

Migration from old plugin

KrakenD Enterprise v2.3 deprecated the no-redirect plugin in favor of the native HTTP client options, and v3.0 removed it. If you used the plugin, apply the following change to your configuration:

"extra_config": {
-    "plugin/http-client": {
-        "name": "no-redirect"
+    "backend/http/client": {
+        "no_redirect": true
        }
    }