From b9f73d89037bdd4c043f6e0fc6aaa34789e0761b Mon Sep 17 00:00:00 2001
From: NagyZoltanPeter <113987313+NagyZoltanPeter@users.noreply.github.com>
Date: Thu, 29 Feb 2024 11:02:07 +0100
Subject: [PATCH] Cross origin request handling for REST server in nwaku will
be included into release 0.26.0. This option to configure this feature is
documented here.
---
docs/guides/nwaku/config-options.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/guides/nwaku/config-options.md b/docs/guides/nwaku/config-options.md
index 56f2d39..0b48cda 100644
--- a/docs/guides/nwaku/config-options.md
+++ b/docs/guides/nwaku/config-options.md
@@ -119,6 +119,7 @@ Here are the available node configuration options, along with their default valu
| `rest-relay-cache-capacity` | `30` | Capacity of the Relay REST API message cache |
| `rest-admin` | `false` | Enable access to REST HTTP Admin API: true\|false |
| `rest-private` | `false` | Enable access to REST HTTP Private API: true\|false |
+| `rest-allow-origin` | | Allow cross-origin requests from the specified origin.
In case REST Api will be used from a browser you need to specify the origin host in order to get proper answer from this node REST HTTP server.
This option maybe repeated and can contain wildcards (?,\*) in defining url and port
Ex.: \"localhost:*\" or \"127.0.0.1:8080\" or allow any sites with \"\*\" |
## Metrics config