From Official Kodi Wiki
Revision as of 15:00, 27 April 2013 by >NedBot (Robot: Cosmetic changes)
Jump to navigation Jump to search

XBMC contains an HTTP-client with which you can add sources in all sections in the XBMC interface.

1 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 url with 'protocol options':

1.1 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:[email protected]: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.

1.2 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.

2 Source formatting

Formatting in sources.xml:

Example (if any variables are not needed, omit the required punctuation):

    <!--to connect as anonymous use "http://ipaddress:port/" or just "http://ipaddress"-->
    <path>http://username:[email protected]:port/directory/|option1=value1&option2=value2</path>

the http protocol options can be set as mentioned in 1.1/1.2.

3 See also