Icecast Server/known reverse proxy restrictions: Difference between revisions
Jump to navigation
Jump to search
(Initial content) |
m (Playlist generation actually works if proxy server is configured correctly.) |
||
| Line 3: | Line 3: | ||
* access.log will always only show the IP address of the reverse proxy instead of listener IP address. | * access.log will always only show the IP address of the reverse proxy instead of listener IP address. | ||
* internal XML tree will only show the IP address of the reverse proxy instead of listener IP address. Both for source clients and for listener clients. | * internal XML tree will only show the IP address of the reverse proxy instead of listener IP address. Both for source clients and for listener clients. | ||
* virtual playlist files will break | * virtual playlist files will break. (Only if proxy server is configured incorrectly.) | ||
* authentication helper will break | * authentication helper will break. (Only if proxy server is configured incorrectly.) | ||
* … | * … | ||
See also [[Icecast_Server/known_https_restrictions|known HTTPS restrictions]], if reverse proxy terminates https. | See also [[Icecast_Server/known_https_restrictions|known HTTPS restrictions]], if reverse proxy terminates https. | ||
Revision as of 02:57, 19 May 2018
This page lists known problems of latest released Icecast when operating behind a reverse proxy:
- access.log will always only show the IP address of the reverse proxy instead of listener IP address.
- internal XML tree will only show the IP address of the reverse proxy instead of listener IP address. Both for source clients and for listener clients.
- virtual playlist files will break. (Only if proxy server is configured incorrectly.)
- authentication helper will break. (Only if proxy server is configured incorrectly.)
- …
See also known HTTPS restrictions, if reverse proxy terminates https.