Icecast Server/known reverse proxy restrictions: Difference between revisions
Jump to navigation
Jump to search
m (Playlist generation actually works if proxy server is configured correctly.) |
(added SOURCE and PUT restrictions) |
||
| Line 5: | Line 5: | ||
* virtual playlist files will break. (Only if proxy server is configured incorrectly.) | * virtual playlist files will break. (Only if proxy server is configured incorrectly.) | ||
* authentication helper will break. (Only if proxy server is configured incorrectly.) | * authentication helper will break. (Only if proxy server is configured incorrectly.) | ||
* HTTP SOURCE connections are very likely to break | |||
* HTTP PUT connections might exhibit problems if the proxying server expects and processes chunked encoding. Chunked encoding will be part of Icecast 2.5 | |||
* … | * … | ||
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. | ||
Latest revision as of 23:53, 18 August 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.)
- HTTP SOURCE connections are very likely to break
- HTTP PUT connections might exhibit problems if the proxying server expects and processes chunked encoding. Chunked encoding will be part of Icecast 2.5
- …
See also known HTTPS restrictions, if reverse proxy terminates https.