From Official Kodi Wiki
Revision as of 20:11, 17 December 2022 by LGoosens (talk | contribs) (Structured markup for clarity)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Home icon grey.png   ▶ 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 url with 'protocol options':

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.

Note: 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.