HTTP: Difference between revisions
No edit summary |
>Ulion No edit summary |
||
Line 1: | Line 1: | ||
<section begin="intro"/>XBMC contains an [[w:HTTP|HTTP]]-client with which you can add sources in all sections in the XBMC interface.<section end="intro"/> | <section begin="intro"/>XBMC contains an [[w:HTTP|HTTP]]-client with which you can add sources in all sections in the XBMC interface.<section end="intro"/> | ||
==HTTP/HTTPS url format== | |||
XBMC supported normal http/https urls, additionally, it support optional options we called as 'protocol options' which user/addons can set so that xbmc 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''' | |||
===XBMC 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 <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) | |||
when the media url is unseekable, addons can set <code>seekable=0</code> protocol options, then xbmc 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. | |||
===Other http protocol options (they are all rfc defined http request headers)=== | |||
* Referer | |||
* User-Agent | |||
* Cookie | |||
* Encoding | |||
For the meanings of these, see RFC 2616. | |||
==Source formatting== | ==Source formatting== | ||
Line 11: | Line 35: | ||
</source> | </source> | ||
</pre> | </pre> | ||
the http protocol options can be set as mentioned in 1.1/1.2. | |||
==See also== | ==See also== |
Revision as of 22:25, 22 April 2013
XBMC contains an HTTP-client with which you can add sources in all sections in the XBMC interface.
HTTP/HTTPS url format
XBMC supported normal http/https urls, additionally, it support optional options we called as 'protocol options' which user/addons can set so that xbmc 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
XBMC 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 xbmc 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
For the meanings of these, see RFC 2616.
Source formatting
Formatting in sources.xml:
Example (if any variables are not needed, omit the required punctuation):
<source> <!--to connect as anonymous use "http://ipaddress:port/" or just "http://ipaddress"--> <path>http://username:password@ipaddress:port/directory/|option1=value1&option2=value2</path> </source>
the http protocol options can be set as mentioned in 1.1/1.2.