HTTP: Difference between revisions
No edit summary |
(→Source formatting: kind of confusing since HTTPS doesn't work in XBMC.) |
||
Line 13: | Line 13: | ||
</pre> | </pre> | ||
Examples of options include "auth", which is required if your HTTP server uses any type of authentication other than basic | Examples of options include "auth", which is required if your HTTP server uses any type of authentication other than basic. 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). | ||
Other options include: | Other options include: |
Revision as of 12:29, 21 September 2012
Template:XBMC wiki toc XBMC contains an HTTP-client with which you can add sources in all sections in the XBMC interface, however as HTTP (Hypertext Transfer Protocol ) is not designed to stream audio/video data it is not recommended that you use it under the Music or Videos sections.
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>
Examples of options include "auth", which is required if your HTTP server uses any type of authentication other than basic. 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).
Other options include:
- Referer
- User-Agent
- Cookie
- Encoding
For the meanings of these, see RFC 2616.