Difference between revisions of "Icecast Server/known reverse proxy restrictions"

From XiphWiki
Jump to navigation Jump to search
(Initial content)
 
(added SOURCE and PUT restrictions)
 
(One intermediate revision by one other user not shown)
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.)
 +
* 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 00:53, 19 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.