Skirda/LiveAtlas
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated Configuring Multiple Servers (markdown)

James Lyne 2022-05-10 13:08:35 +01:00
parent 108a12e5c5
commit 3b2f6cacbd
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Configuring-Multiple-Servers.md

@ -20,7 +20,7 @@ This subdirectory-based approach was chosen for its relative simplicity and beca
- If your servers are accessed via a [different origin](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy#definition_of_an_origin) to LiveAtlas itself, then you will need to ensure [CORS headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) are configured correctly.
Requests for map information should return an appropriate `Access-Control-Allow-Origin` header as well as `Access-Control-Allow-Credentials: true`. Headers for the Dynmap internal webserver can be configured using Dynmap's [http-response-headers setting](https://github.com/webbukkit/dynmap/wiki/Configuration.txt#http-response-headers)
Requests for map information should return an appropriate `Access-Control-Allow-Origin` header as well as `Access-Control-Allow-Credentials: true`. Headers for the Dynmap internal webserver can be configured using Dynmap's [http-response-headers setting](https://github.com/webbukkit/dynmap/wiki/Configuration.txt#http-response-headers)
Alternatively, you can configure your webserver as a reverse proxy and make all individual servers accessible from the same origin LiveAtlas is hosted on, which will avoid this issue.