Make references to image/ and jsonrpc relative

[lozbrown]

links to image and jsonrpc start with a leading slash, this makes proxying more complicated.

I think all that is required here is to remove the leading slash when proxying

[lozbrown]

Similar issues have been raised against Chorus 1
jez500/chorus#77
jez500/chorus#78

The above includes this slightly more in depth description:

Using '/jsonrpc' can cause problems if you have a proxy infront of xbmc and it already has a relative URL.

Simply removing the '/' form the front of the jsonrpc url will fix it (and does not break non-proxied access).
The problem is if you already have a relative url (https://mydomain.com/xbmcbox), then /jsonrpc will try to hit https://mydomain.com/jsonrpc (gets 404). If you change it to 'jsonrpc', then it will work correctly and hit https://mydomain.com/xbmcbox/jsonrpc

The issue for images is essentially the same.

I've worked around that slightly in #133 by re-pointing those locations to the kodi webserver as well but its really not good practice becuase it prevents the owner using /images or /jasonrpc for their own things.

[jez500]

I'm thinking the best solution for this is to add the ability to override the /jsonrpc and /images paths in the settings page. Would that solve this issue?

[lozbrown]

It would but it seems like an unnecessarily complicated solution for both you as the implementer and for the end users. This should in theory be just a string operation to strip the leading slash from certain uris. in theory this should not break anything else.

The above requires capturing an additional variable in setting and then prepending that to all the above mentioned URIs,, they will probably have to experiment to work out whether they need to add the leading or training slash to those settings items.