Login to Media Browser fails with rewrite to https
Posted: Fri Jan 11, 2013 8:57 amHi all,
I´ve successfully installed serviio and in the next step I wanted to give the MediaBrowser a try.
My users must access the MediaBrowser through apache mod_proxy which I have configured according to viewtopic.php?f=5&t=6852&p=49666#p49850. In addition I have configured apache to rewrite every http request to https.
This seems to be a problem as no one is able to sign in to the MediaBrowser.
As I can see in chrome developer tools the URL http://www.example.net/cds/login is requested when the button 'Sign in' is pressed and the Status is (canceled).
The rewrite seems to break to communication. To prove my assumption I configured apache NOT to rewrite every http request to https and everything works fine.
I wondered why only the request to /cds/login was http and found out the 'http://' used for the request is hard coded in media-browser.js.
Why is the http:// hard coded inside the media-browser.js? Isn´t it better and even correct to use location.protocol?
I was wondering nobody else had this issue before, but I couldn´t find any post. Hope this can be solved, as I am not willing to sacrifice https communication.
Thanks for any help!
Regards
Ingo
I´ve successfully installed serviio and in the next step I wanted to give the MediaBrowser a try.
My users must access the MediaBrowser through apache mod_proxy which I have configured according to viewtopic.php?f=5&t=6852&p=49666#p49850. In addition I have configured apache to rewrite every http request to https.
This seems to be a problem as no one is able to sign in to the MediaBrowser.
As I can see in chrome developer tools the URL http://www.example.net/cds/login is requested when the button 'Sign in' is pressed and the Status is (canceled).
The rewrite seems to break to communication. To prove my assumption I configured apache NOT to rewrite every http request to https and everything works fine.
I wondered why only the request to /cds/login was http and found out the 'http://' used for the request is hard coded in media-browser.js.
- Code:
var folderListUrl = "http://"
+ host
+ "/cds/browse/flv_player/{folderId}/BrowseDirectChildren/containers/0/0?authToken={token}";
var folderItemsUrl = "http://"
+ host
+ "/cds/browse/flv_player/{folderId}/BrowseDirectChildren/items/{offset}/{limit}?authToken={token}";
var itemMetadataUrl = "http://"
+ host
+ "/cds/browse/flv_player/{objectId}/BrowseMetadata/all/0/1?authToken={token}";
var loginUrl = "http://" + host + "/cds/login";
var logoutUrl = "http://" + host + "/cds/logout";
Why is the http:// hard coded inside the media-browser.js? Isn´t it better and even correct to use location.protocol?
I was wondering nobody else had this issue before, but I couldn´t find any post. Hope this can be solved, as I am not willing to sacrifice https communication.
Thanks for any help!
Regards
Ingo