Sources.xml/Types - Revision history

Grandmabetty: /* WebDAV */

2025-03-18T13:43:34Z

WebDAV

← Older revision		Revision as of 13:43, 18 March 2025
Line 190:		Line 190:

	=== WebDAV ===		=== WebDAV ===
	~~Please note that you~~ can either connect to a WebDAV-Server via an unencrypted ''dav'' (HTTP) or an encrypted ''davs'' (HTTPS) connection.		You can either connect Kodi to a WebDAV-Server via an unencrypted ''dav'' (HTTP) or an encrypted ''davs'' (HTTPS) connection.
	If you choose to connect ~~via~~ your WebDAV server's IP address ~~instad~~ of its hostname, then you are forced to choose an unencrypted ''dav'' (HTTP) connection.		If you choose to connect Kodi to your WebDAV server via its IP address instead of its hostname, then you are forced to choose an unencrypted ''dav'' (HTTP) connection.
	This is due to Kodi's WebDAV client implementation, ~~on which~~ an encrypted ''davs'' (HTTPS) connection is always associated to a vaild SSL certificate which yet is associated to a WebDAV server's host-/domainname.		This is due to Kodi's WebDAV client implementation, where an encrypted ''davs'' (HTTPS) connection is always associated to a vaild SSL certificate which yet is associated to a WebDAV server's host-/domainname.
	In other words: If you choose to connect via an encrypted ''davs'' (HTTPS) connection, you are forced to connect via your WebDAV server's host-/domainname instead of its IP address '''and''' you will need a valid SSL certificate securing/validating your ''davs'' (HTTPS) connection (Depending on whether you are using a reverse web proxy server or not and on how it is configured, the according SSL certificate mostly has to be installed directly on your WebDAV server.). Be aware that self-signed certificates do '''not''' work as they will be revoked by the Kodi WebDAV client, you can get a valid SSL certificate provided by an official certificate authority, for example "Let's encrypt".		In other words: If you choose to connect via an encrypted ''davs'' (HTTPS) connection, you are forced to connect via your WebDAV server's host-/domainname instead of its IP address '''and''' you will need a valid SSL certificate securing/validating your ''davs'' (HTTPS) connection. Depending on whether you are using a reverse web proxy server or not and on how it is configured, the according SSL certificate mostly has to be installed directly on your WebDAV server. Be aware that self-signed certificates do '''not''' work as they will be revoked by the Kodi WebDAV client, you can get a valid SSL certificate provided by an official certificate authority, for example "Let's encrypt".

	Example unencrypted ''dav'' (HTTP):		Example unencrypted ''dav'' (HTTP):

Grandmabetty: /* WebDAV */

2025-03-18T13:40:18Z

WebDAV

← Older revision		Revision as of 13:40, 18 March 2025
Line 193:		Line 193:
	If you choose to connect via your WebDAV server's IP address instad of its hostname, then you are forced to choose an unencrypted ''dav'' (HTTP) connection.		If you choose to connect via your WebDAV server's IP address instad of its hostname, then you are forced to choose an unencrypted ''dav'' (HTTP) connection.
	This is due to Kodi's WebDAV client implementation, on which an encrypted ''davs'' (HTTPS) connection is always associated to a vaild SSL certificate which yet is associated to a WebDAV server's host-/domainname.		This is due to Kodi's WebDAV client implementation, on which an encrypted ''davs'' (HTTPS) connection is always associated to a vaild SSL certificate which yet is associated to a WebDAV server's host-/domainname.
	In other words: If you choose to connect via an encrypted ''davs'' (HTTPS) connection, you are forced to connect via your WebDAV server's host-/domainname instead of its IP address '''and''' you will need a valid SSL certificate securing/validating your ''davs'' (HTTPS) connection (~~The according SSL certificate is mostly installed directly~~ on ~~your WebDAV server, depending~~ whether you are using a reverse web proxy server or not and on how it is configured).		In other words: If you choose to connect via an encrypted ''davs'' (HTTPS) connection, you are forced to connect via your WebDAV server's host-/domainname instead of its IP address '''and''' you will need a valid SSL certificate securing/validating your ''davs'' (HTTPS) connection (Depending on whether you are using a reverse web proxy server or not and on how it is configured, the according SSL certificate mostly has to be installed directly on your WebDAV server.). Be aware that self-signed certificates do '''not''' work as they will be revoked by the Kodi WebDAV client, you can get a valid SSL certificate provided by an official certificate authority, for example "Let's encrypt".
	Be aware that self-signed certificates do not work as they will be revoked by the Kodi WebDAV client, you can get a valid SSL certificate provided by an official certificate authority, for example "Let's encrypt".

	Example unencrypted ''dav'' (HTTP):		Example unencrypted ''dav'' (HTTP):

Grandmabetty: /* Sources with multiple paths / targets */

2025-03-18T13:37:29Z

Sources with multiple paths / targets

← Older revision		Revision as of 13:37, 18 March 2025
Line 5:		Line 5:
	It is possible to let a media source point to more than one target or path. You can accomplish this through the User Interface or by directly editing the sources.xml. One example from the Videos section of the default Sources.xml file.		It is possible to let a media source point to more than one target or path. You can accomplish this through the User Interface or by directly editing the sources.xml. One example from the Videos section of the default Sources.xml file.
	<pre>		<pre>
	<source>		<source>
	<name>01 Movies</name>		<name>01 Movies</name>
	<path pathversion="1">F:\Kodi\Movies HD\</path>		<path pathversion="1">F:\Kodi\Movies HD\</path>
	<path pathversion="1">E:\Kodi\Movies SD\Movies New\</path>		<path pathversion="1">E:\Kodi\Movies SD\Movies New\</path>
	</source>		</source>
	</pre>		</pre>
	The '''pathversion="1"''' parameter means it was written with a more recent version of Kodi. It's to ensure that saved paths can be reliably updated if/when a new way to store them is implemented (e.g. old paths using Q: are now stored using special://xbmc etc).		The '''pathversion="1"''' parameter means it was written with a more recent version of Kodi. It's to ensure that saved paths can be reliably updated if/when a new way to store them is implemented (e.g. old paths using Q: are now stored using special://xbmc etc).

Grandmabetty: /* WebDAV */

2025-03-18T09:12:46Z

WebDAV

← Older revision		Revision as of 09:12, 18 March 2025
Line 194:		Line 194:
	This is due to Kodi's WebDAV client implementation, on which an encrypted ''davs'' (HTTPS) connection is always associated to a vaild SSL certificate which yet is associated to a WebDAV server's host-/domainname.		This is due to Kodi's WebDAV client implementation, on which an encrypted ''davs'' (HTTPS) connection is always associated to a vaild SSL certificate which yet is associated to a WebDAV server's host-/domainname.
	In other words: If you choose to connect via an encrypted ''davs'' (HTTPS) connection, you are forced to connect via your WebDAV server's host-/domainname instead of its IP address '''and''' you will need a valid SSL certificate securing/validating your ''davs'' (HTTPS) connection (The according SSL certificate is mostly installed directly on your WebDAV server, depending whether you are using a reverse web proxy server or not and on how it is configured).		In other words: If you choose to connect via an encrypted ''davs'' (HTTPS) connection, you are forced to connect via your WebDAV server's host-/domainname instead of its IP address '''and''' you will need a valid SSL certificate securing/validating your ''davs'' (HTTPS) connection (The according SSL certificate is mostly installed directly on your WebDAV server, depending whether you are using a reverse web proxy server or not and on how it is configured).
	Be aware that self-signed certificates do not work as they will be revoked by the Kodi WebDAV client~~! You~~ can get a valid SSL certificate provided by an official certificate authority, for example "Let's encrypt".		Be aware that self-signed certificates do not work as they will be revoked by the Kodi WebDAV client, you can get a valid SSL certificate provided by an official certificate authority, for example "Let's encrypt".

	Example unencrypted ''dav'' (HTTP):		Example unencrypted ''dav'' (HTTP):

Grandmabetty: /* HDHomeRun */

2025-03-18T09:10:26Z

HDHomeRun

← Older revision		Revision as of 09:10, 18 March 2025
Line 236:		Line 236:

	<pre>		<pre>
	<source>		<source>
	<name>HDHomeRun</name>		<name>HDHomeRun</name>
	<path>hdhomerun://</path>		<path>hdhomerun://</path>
	</source>		</source>
	</pre>		</pre>

Grandmabetty: /* RSS Feeds */

2025-03-18T09:10:04Z

RSS Feeds

← Older revision		Revision as of 09:10, 18 March 2025
Line 183:		Line 183:

	<pre>		<pre>
	<source>		<source>
	<name>RSS Feed</name>		<name>RSS Feed</name>
	<path>rss://</path>		<path>rss://</path>
	</source>		</source>
	</pre>		</pre>

Grandmabetty: /* HDHomeRun */

2025-03-18T09:08:17Z

HDHomeRun

← Older revision		Revision as of 09:08, 18 March 2025
Line 234:		Line 234:
	=== HDHomeRun ===		=== HDHomeRun ===
	This type of media source will connect to a HDHomeRun (Networked Digital Cable TV/HDTV Tuner) box and allows you to watch Live TV directly from Kodi.<br />		This type of media source will connect to a HDHomeRun (Networked Digital Cable TV/HDTV Tuner) box and allows you to watch Live TV directly from Kodi.<br />


	<pre>		<pre>

Grandmabetty: /* WebDAV */

2025-03-18T09:06:54Z

WebDAV

← Older revision		Revision as of 09:06, 18 March 2025
Line 198:		Line 198:
	Example unencrypted ''dav'' (HTTP):		Example unencrypted ''dav'' (HTTP):
	<pre>		<pre>
	<source>		<source>
	<name>Remote WebDAV videos</name>		<name>Remote WebDAV videos</name>
	<path>dav://username:password@server.com/share/videos/</path>		<path>dav://username:password@server.com/share/videos/</path>
	</source>		</source>
	</pre>		</pre>

	Example encrypted ''davs'' (HTTPS):		Example encrypted ''davs'' (HTTPS):
	<pre>		<pre>
	<source>		<source>
	<name>Remote WebDAV videos</name>		<name>Remote WebDAV videos</name>
	<path>davs://username:password@server.com/share/videos/</path>		<path>davs://username:password@server.com/share/videos/</path>
	</source>		</source>
	</pre>		</pre>

Grandmabetty: /* SFTP (SSH File Transfer Protocol) Client */

2025-03-18T09:06:13Z

SFTP (SSH File Transfer Protocol) Client

← Older revision		Revision as of 09:06, 18 March 2025
Line 147:		Line 147:

	<pre>		<pre>
	<source>		<source>
	<name>Remote SFTP Videos</name>		<name>Remote SFTP Videos</name>
	<path>sftp://username:password@server.com/share/videos/</path>		<path>sftp://username:password@server.com/share/videos/</path>
	</source>		</source>
	</pre>		</pre>

Grandmabetty: /* WebDAV */

2025-03-18T09:05:18Z

WebDAV

← Older revision		Revision as of 09:05, 18 March 2025
Line 200:		Line 200:
	<source>		<source>
	<name>Remote WebDAV videos</name>		<name>Remote WebDAV videos</name>
	<path>dav://username:password@server.com/share/videos/</path>		<path>dav://username:password@server.com/share/videos/</path>
	</source>		</source>
	</pre>		</pre>
Line 208:		Line 208:
	<source>		<source>
	<name>Remote WebDAV videos</name>		<name>Remote WebDAV videos</name>
	<path>davs://username:password@server.com/share/videos/</path>		<path>davs://username:password@server.com/share/videos/</path>
	</source>		</source>
	</pre>		</pre>