Skip to main content

Blocks: Advanced Configuration

Log in to add to favourites

Page last updated 23 January 2026

This guide covers advanced Block configuration options, including manifest.json, ports, routing behaviour, and static assets.


The manifest.json file

manifest.json is optional. Only include it if you need to change default Block behaviour.

If used, it must be placed at the root of the Docker image.

Example:

JSON
{ "port": 5000, "static_paths": ["/assets"], "enableFullUriRouting": true }

Port configuration

port

  • Optional
  • Default: 3001
  • Use only if your application listens on a different port

Example:

JSON
{ "port": 5000 }

Routing behaviour

enableFullUriRouting

  • Optional
  • Default: false

Controls how the original request path is passed to your application.

When enabled, the application receives the original path directly.

When disabled, the original path is provided as a query parameter.

Example request:

https://www.website.com/products/item-1

With enableFullUriRouting: true:

http://<block-host>/products/item-1?nodeId=xxx&entryId=yyy

With enableFullUriRouting: false:

http://<block-host>/?originPath=/products/item-1&nodeId=xxx&entryId=yyy

Enable this if your application implements its own routing logic or expects routes to be hit directly.


Static assets

Blocks rewrite static asset URLs to include a version-specific prefix.

Default static paths:

  • /static
  • /image-library

You can add additional static root paths using static_paths.

Rules:

  • Paths must be explicit root paths (for example /assets)
  • Wildcards are not supported
  • All child paths are included automatically

Example:

JSON
{ "static_paths": ["/assets"] }

Why assets are rewritten

Rewriting allows multiple Block versions to be previewed on the same URL without cache conflicts. Each Block version resolves to its own asset URLs, preventing browsers or CDNs from serving assets from a different version.


Direct access to static files

Static asset rewriting only occurs when requests pass through a Block.

Direct requests to static files without the rewritten prefix may return 404.

If direct access is required, expose static content via an application endpoint and serve it explicitly.

Still need help?

If you still need help after reading this article, don't hesitate to reach out to the Contensis community on Slack or raise a support ticket to get help from our team.
New support request