Congegni/sintonia
7
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Document CORS configuration better

Browse source 
Fixes #917
This commit is contained in:
Kyle Robbertze 2020-01-07 09:36:03 +02:00
parent 76ba139be5
commit 5469b0874c
2 changed files with 15 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/manual/general/index.md
View file

@ -50,7 +50,9 @@ wish. (There is more about this feature in the
*Advanced Configuration* section of this book).
The **Allowed CORS URLs** is intended to deal with situations where you want a
remote site with a different domain to access the API.
remote site with a different domain to access the API. This is relevant when
there is a reverse proxy server in front of LibreTime. If you are using a
reverse proxy, the URLs that will be used to access it should be added here.
The **Display login button on your Radio Page?** will determine whether visitors
to your site see a link to login. If this is disabled DJs and admins will need

12
docs/manual/getting-started/index.md
View file

@ -94,3 +94,15 @@ your LibreTime server has made to this Icecast server. If you have only just
installed LibreTime, there may not be any media playing out yet.
![](static/Screenshot293-Icecast_status_page.png)
Reverse Proxy Connections
-------------------------
In some deployments, the LibreTime server is deployed behind a reverse proxy,
for example in containerization use-cases such as Docker and LXC. LibreTime
makes extensive use of its API for some site functionality, which causes
[Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)
to occur. By default, CORS requests are blocked by your browser and the origins
need to be added to the **Allowed CORS URLs** block in
[**General Settings**](/manual/general/). These origins should include any
domains that will be used externally to connect to your reverse proxy that you
want handled by LibreTime.