HTTP: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
{{mininav| [[Media sources]] | [[File sharing]] }} | {{mininav| [[Media sources]] | [[File sharing]] }} | ||
<section begin="intro"/> | <section begin="intro"/>Kodi contains an [[w:HTTP|HTTP]]-client with which you can add sources in all sections in the Kodi interface.<section end="intro"/> | ||
== HTTP/HTTPS url format == | == HTTP/HTTPS url format == | ||
Kodi supported normal http/https urls, additionally, it support optional options we called as 'protocol options' which user/addons can set so that Kodi can full simulate the browser operations with specified http request header values. | |||
* normal http url format: | * normal http url format: | ||
http[s]://[username[:password]@]host[:port]/directory/file?a=b&c=d | http[s]://[username[:password]@]host[:port]/directory/file?a=b&c=d | ||
| Line 10: | Line 10: | ||
http[s]://[username[:password]@]host[:port]/directory/file?a=b&c=d'''|option1=value1&option2=value2''' | http[s]://[username[:password]@]host[:port]/directory/file?a=b&c=d'''|option1=value1&option2=value2''' | ||
=== Kodi | === Kodi supported special http protocol options === | ||
* auth | * auth | ||
which is required if your HTTP server uses any type of authentication other than basic (which is, in fact, unsafe unless used over HTTPS). E.g. if your HTTP server uses digest authentication, use <code><nowiki>http://username:password@host:port/directory/|auth=digest</nowiki></code>. For maximum flexibility, use <code>auth=any</code> or <code>auth=anysafe</code> (i.e. anything other than basic). | which is required if your HTTP server uses any type of authentication other than basic (which is, in fact, unsafe unless used over HTTPS). E.g. if your HTTP server uses digest authentication, use <code><nowiki>http://username:password@host:port/directory/|auth=digest</nowiki></code>. For maximum flexibility, use <code>auth=any</code> or <code>auth=anysafe</code> (i.e. anything other than basic). | ||
* seekable (13.0+ Gotham, since git bb79b32b) | * seekable (13.0+ Gotham, since git bb79b32b) | ||
when the media url is unseekable, addons can set <code>seekable=0</code> protocol options, then | when the media url is unseekable, addons can set <code>seekable=0</code> protocol options, then Kodi won't try to seek on that url. | ||
if you set it in frodo or earlier, it will add a http header '<code>seekable: 0</code>' in the http request, it's harmless. | if you set it in frodo or earlier, it will add a http header '<code>seekable: 0</code>' in the http request, it's harmless. | ||
| Line 29: | Line 29: | ||
== See also == | == See also == | ||
* [[WebDAV]] | * [[WebDAV]] | ||
{{ | |||
{{Helix updated}} | |||
[[Category:File sharing]] | [[Category:File sharing]] | ||
[[Category:Manual]] | [[Category:Manual]] | ||
Revision as of 06:32, 16 May 2015
|
 Media sources |
File sharing |
HTTP
|
Kodi contains an HTTP-client with which you can add sources in all sections in the Kodi interface.
HTTP/HTTPS url format
Kodi supported normal http/https urls, additionally, it support optional options we called as 'protocol options' which user/addons can set so that Kodi can full simulate the browser operations with specified http request header values.
- normal http url format:
http[s]://[username[:password]@]host[:port]/directory/file?a=b&c=d
- http url with 'protocol options':
http[s]://[username[:password]@]host[:port]/directory/file?a=b&c=d|option1=value1&option2=value2
Kodi supported special http protocol options
- auth
which is required if your HTTP server uses any type of authentication other than basic (which is, in fact, unsafe unless used over HTTPS). E.g. if your HTTP server uses digest authentication, use http://username:password@host:port/directory/|auth=digest. For maximum flexibility, use auth=any or auth=anysafe (i.e. anything other than basic).
- seekable (13.0+ Gotham, since git bb79b32b)
when the media url is unseekable, addons can set seekable=0 protocol options, then Kodi won't try to seek on that url.
if you set it in frodo or earlier, it will add a http header 'seekable: 0' in the http request, it's harmless.
Other http protocol options (they are all rfc defined http request headers)
- Referer
- User-Agent
- Cookie
- Encoding
- any other http request headers defined in rfc.
For the meanings of these, see RFC 2616.