2014-01-22, 11:47
Important notice to existing users
The proxy location feature has been slightly modified so that it only exposes the /vfs part of XBMC's web server. This way you won't have to leave your whole API exposed to the internet, just the virtual filesystem. The downside to this change is that you will have to consult the README again on how to configure the proxy location. Nothing difficult, it boils down to adding "/vfs" to the "ProxyPass" and "ProxyPassReverse" directives in your Apache configurations.
To clarify, if you previously had this in your configuration:
you will have to change it to this:
If you don't use the proxy location feature you can safely ignore this.
The proxy location feature has been slightly modified so that it only exposes the /vfs part of XBMC's web server. This way you won't have to leave your whole API exposed to the internet, just the virtual filesystem. The downside to this change is that you will have to consult the README again on how to configure the proxy location. Nothing difficult, it boils down to adding "/vfs" to the "ProxyPass" and "ProxyPassReverse" directives in your Apache configurations.
To clarify, if you previously had this in your configuration:
Quote:<Location /xbmc>
ProxyPass http://xbmc.example.com:8080
ProxyPassReverse http://xbmc.example.com:8080
RequestHeader set Authorization "Basic eGJtYzp4Ym1j"
</Location>
you will have to change it to this:
Quote:<Location /xbmc-vfs>
ProxyPass http://xbmc.example.com:8080/vfs
ProxyPassReverse http://xbmc.example.com:8080/vfs
RequestHeader set Authorization "Basic eGJtYzp4Ym1j"
</Location>
If you don't use the proxy location feature you can safely ignore this.