Webserver - Revision history

Bramp: /* Hints */ Fix up the formatting of the example Apache config.

2022-01-27T22:29:13Z

Hints: Fix up the formatting of the example Apache config.

← Older revision		Revision as of 22:29, 27 January 2022
Line 8:		Line 8:
	* On Linux, ports below 1024 require super-user privileges and are therefore not available to {{kodi}}. For Linux, you must change the port number to a port number above 1024 that's not in use on your computer, like 1485, 1588 or 1066 for example. Those 3 port numbers have no popular uses registered with IANA, the Internet Assigned Numbers Authority. Remote control via HTTP will see the web server with whatever port you choose.		* On Linux, ports below 1024 require super-user privileges and are therefore not available to {{kodi}}. For Linux, you must change the port number to a port number above 1024 that's not in use on your computer, like 1485, 1588 or 1066 for example. Those 3 port numbers have no popular uses registered with IANA, the Internet Assigned Numbers Authority. Remote control via HTTP will see the web server with whatever port you choose.
	* For use in a virtual hosts environment in Apache, the following directives can be used:		* For use in a virtual hosts environment in Apache, the following directives can be used:
	:<syntaxhighlight lang="apache~~" enclose="div~~">
	#Kodi configuration~~, replace~~ kodiserver with ~~the~~ actual ~~server name~~.		<syntaxhighlight lang="apache">
			# Kodi configuration
			# Replace kodiserver with actual names.

			ServerName kodiserver
	DocumentRoot /		DocumentRoot /
	LogLevel emerg		LogLevel emerg
Line 17:		Line 21:
	ProxyPassReverse / http://kodiserver:8080/		ProxyPassReverse / http://kodiserver:8080/
	<Directory "/">		<Directory "/">
	allow from all		allow from all
	Options +Indexes		Options +Indexes
	</Directory>		</Directory>
	~~ServerName servername~~
	AllowEncodedSlashes On		AllowEncodedSlashes On
	</syntaxhighlight>		</syntaxhighlight>
	~~Allow EncodedSlashes~~ is necessary to have webpages work properly.
			AllowEncodedSlashes is necessary to have webpages work properly.

	nocanon is used to disable url encoding use this if images are not showing in the webbrowser.		nocanon is used to disable url encoding use this if images are not showing in the webbrowser.

Karellen at 02:52, 23 July 2020

2020-07-23T02:52:07Z

← Older revision		Revision as of 02:52, 23 July 2020
Line 35:		Line 35:

	=== Webinterface addons /addons ===		=== Webinterface addons /addons ===
	Requesting the /addons path will show a HTML page with a list of all installed and available ~~[[:Category:Web interface add-ons\|~~webinterface addons]]. By appending the identifier of one of the webinterface addons to the /addons path it is possible to access all the available webinterfaces without configuring them in the settings.		Requesting the /addons path will show a HTML page with a list of all installed and available webinterface addons. By appending the identifier of one of the webinterface addons to the /addons path it is possible to access all the available webinterfaces without configuring them in the settings.

	=== Image cache /image ===		=== Image cache /image ===
Line 50:		Line 50:
	As of XBMC v12 Frodo, in an effort to make the Virtual File System service more secure (in Eden and before it allowed access to literally any file on the local hard disc and on network shares accessible to {{kodi}}) the access has been limited to files within directories that have been specified by the user as sources (video, music, files, programs) in {{kodi}}.		As of XBMC v12 Frodo, in an effort to make the Virtual File System service more secure (in Eden and before it allowed access to literally any file on the local hard disc and on network shares accessible to {{kodi}}) the access has been limited to files within directories that have been specified by the user as sources (video, music, files, programs) in {{kodi}}.

	~~== See also ==~~
	* [[Remote controls]]
	* [[JSON-RPC API]]
	* [[Web interface]]
	* [[:Category:Web interface add-ons]]
	* [[:Category:Standalone web interfaces]]

	{{Updated\|16}}		{{Updated\|16}}

	~~[[Category:Manual]]~~

Tcplomp: Added nocanon

2019-09-25T10:31:11Z

Added nocanon

← Older revision		Revision as of 10:31, 25 September 2019
Line 24:		Line 24:
	</syntaxhighlight>		</syntaxhighlight>
	Allow EncodedSlashes is necessary to have webpages work properly.		Allow EncodedSlashes is necessary to have webpages work properly.
	nocanon is used to disable url encoding ~~(URLs are passed on without URL encoding),~~ use this if images are not showing
			nocanon is used to disable url encoding use this if images are not showing in the webbrowser.

	== Services ==		== Services ==

Tcplomp: /* Hints */

2019-09-25T10:29:49Z

Hints

← Older revision		Revision as of 10:29, 25 September 2019
Line 14:		Line 14:
	ErrorLog /var/log/apache2/kodiserver_error.log		ErrorLog /var/log/apache2/kodiserver_error.log
	CustomLog /var/log/apache2/kodiserver_access.log "vhost_combined"		CustomLog /var/log/apache2/kodiserver_access.log "vhost_combined"
	ProxyPass / http://kodiserver:8080/		ProxyPass / http://kodiserver:8080/ nocanon
	ProxyPassReverse / http://kodiserver:8080/		ProxyPassReverse / http://kodiserver:8080/
	<Directory "/">		<Directory "/">
Line 24:		Line 24:
	</syntaxhighlight>		</syntaxhighlight>
	Allow EncodedSlashes is necessary to have webpages work properly.		Allow EncodedSlashes is necessary to have webpages work properly.
			nocanon is used to disable url encoding (URLs are passed on without URL encoding), use this if images are not showing

	== Services ==		== Services ==

Ned Scott: /* See also */

2016-06-01T22:34:47Z

Ned Scott: /* See also */

2016-06-01T22:34:31Z

B52apl: /* Hints */

2016-04-02T14:12:45Z

Hints

← Older revision		Revision as of 14:12, 2 April 2016
Line 6:		Line 6:
	=== Hints ===		=== Hints ===
	* If the webserver fails to start make sure you use a port that is not blocked by your firewall and is not used by any other process running on the same machine. If there is another webserver like Apache running on the same machine it is very likely that port 80 (HTTP default port) is already used.		* If the webserver fails to start make sure you use a port that is not blocked by your firewall and is not used by any other process running on the same machine. If there is another webserver like Apache running on the same machine it is very likely that port 80 (HTTP default port) is already used.
	* On Linux, ports below 1024 require super-user privileges and are therefore not available to {{kodi}}. For Linux, you must change the port number to a port number above 1024 that's not in use on your computer, like 1485, 1588 or 1066 for example. ~~The remote~~ control via HTTP will see the web server with whatever port you choose.		* On Linux, ports below 1024 require super-user privileges and are therefore not available to {{kodi}}. For Linux, you must change the port number to a port number above 1024 that's not in use on your computer, like 1485, 1588 or 1066 for example. Those 3 port numbers have no popular uses registered with IANA, the Internet Assigned Numbers Authority. Remote control via HTTP will see the web server with whatever port you choose.
	* For use in a virtual hosts environment in Apache, the following directives can be used:		* For use in a virtual hosts environment in Apache, the following directives can be used:
	:<syntaxhighlight lang="apache" enclose="div">		:<syntaxhighlight lang="apache" enclose="div">

B52apl: /* Hints */

2016-04-02T14:08:40Z

Hints

← Older revision		Revision as of 14:08, 2 April 2016
Line 6:		Line 6:
	=== Hints ===		=== Hints ===
	* If the webserver fails to start make sure you use a port that is not blocked by your firewall and is not used by any other process running on the same machine. If there is another webserver like Apache running on the same machine it is very likely that port 80 (HTTP default port) is already used.		* If the webserver fails to start make sure you use a port that is not blocked by your firewall and is not used by any other process running on the same machine. If there is another webserver like Apache running on the same machine it is very likely that port 80 (HTTP default port) is already used.
	* On Linux ports below 1024 require super-user privileges and are therefore not available to {{kodi}}. For Linux, you ~~can~~ change the port number to a port number above 1024 that's not in use, like 1066 for example. ~~Control programs~~ will see the web server with whatever port ~~number~~ you choose.		* On Linux, ports below 1024 require super-user privileges and are therefore not available to {{kodi}}. For Linux, you must change the port number to a port number above 1024 that's not in use on your computer, like 1485, 1588 or 1066 for example. The remote control via HTTP will see the web server with whatever port you choose.
	* For use in a virtual hosts environment in Apache, the following directives can be used:		* For use in a virtual hosts environment in Apache, the following directives can be used:
	:<syntaxhighlight lang="apache" enclose="div">		:<syntaxhighlight lang="apache" enclose="div">

B52apl: /* Hints */

2016-04-02T13:27:08Z

Hints

← Older revision		Revision as of 13:27, 2 April 2016
Line 6:		Line 6:
	=== Hints ===		=== Hints ===
	* If the webserver fails to start make sure you use a port that is not blocked by your firewall and is not used by any other process running on the same machine. If there is another webserver like Apache running on the same machine it is very likely that port 80 (HTTP default port) is already used.		* If the webserver fails to start make sure you use a port that is not blocked by your firewall and is not used by any other process running on the same machine. If there is another webserver like Apache running on the same machine it is very likely that port 80 (HTTP default port) is already used.
	* On Linux ports below 1024 require super-user privileges and are therefore not available to {{kodi}}. For Linux, you can change the port number to a port number above 1024 that's not in use, like 1066 for example.		* On Linux ports below 1024 require super-user privileges and are therefore not available to {{kodi}}. For Linux, you can change the port number to a port number above 1024 that's not in use, like 1066 for example. Control programs will see the web server with whatever port number you choose.
	* For use in a virtual hosts environment in Apache, the following directives can be used:		* For use in a virtual hosts environment in Apache, the following directives can be used:
	:<syntaxhighlight lang="apache" enclose="div">		:<syntaxhighlight lang="apache" enclose="div">

B52apl: /* Hints */

2016-04-02T13:24:31Z

Hints

← Older revision		Revision as of 13:24, 2 April 2016
Line 6:		Line 6:
	=== Hints ===		=== Hints ===
	* If the webserver fails to start make sure you use a port that is not blocked by your firewall and is not used by any other process running on the same machine. If there is another webserver like Apache running on the same machine it is very likely that port 80 (HTTP default port) is already used.		* If the webserver fails to start make sure you use a port that is not blocked by your firewall and is not used by any other process running on the same machine. If there is another webserver like Apache running on the same machine it is very likely that port 80 (HTTP default port) is already used.
	* On Linux ports below 1024 require super-user privileges and are therefore not available to {{kodi}}. For Linux, change the port number to a port number above 1024 that's not in use, like 1066 for example.		* On Linux ports below 1024 require super-user privileges and are therefore not available to {{kodi}}. For Linux, you can change the port number to a port number above 1024 that's not in use, like 1066 for example.
	* For use in a virtual hosts environment in Apache, the following directives can be used:		* For use in a virtual hosts environment in Apache, the following directives can be used:
	:<syntaxhighlight lang="apache" enclose="div">		:<syntaxhighlight lang="apache" enclose="div">

← Older revision		Revision as of 22:34, 1 June 2016
Line 52:		Line 52:
	* [[JSON-RPC API]]		* [[JSON-RPC API]]
	* [[Web interface]]		* [[Web interface]]
	* [[Add-on:Default web interface]]
	* [[:Category:Web interface add-ons]]		* [[:Category:Web interface add-ons]]
	* [[:Category:Standalone web interfaces]]		* [[:Category:Standalone web interfaces]]

← Older revision		Revision as of 22:34, 1 June 2016
Line 49:		Line 49:

	== See also ==		== See also ==
			* [[Remote controls]]
	* [[JSON-RPC API]]		* [[JSON-RPC API]]
	* [[Web Server HTTP API]] - Depreciated since XBMC v10, removed since XBMC v12
	* [[Web interface]]		* [[Web interface]]
	* [[Add-on:Default web interface]]		* [[Add-on:Default web interface]]
Line 56:		Line 56:
	* [[:Category:Standalone web interfaces]]		* [[:Category:Standalone web interfaces]]

	{{~~Helix updated~~}}		{{Updated\|16}}

	[[Category:Manual]]		[[Category:Manual]]