Testing the library we have found out that the different libraries (Nova, Glance, Volume) use the 'adminURL' parameter instead of the 'publicURL' parameter.
If the application runs inside the corporate firewall, then probably internalURL fits better.
If the application runs outside the corporate firewall (in a remote browser, for example), then probably publicURL is a better choice.
Probably the library should allow some kind of configuration to support both scenarios.
In our case, we are testing horizon-js in the same server of an Apache server acting as a proxy to the different services (Glance,Nova, Volume and Keystone). The apache proxy endpoints are the publicURL configured in keystone.
Yes, it's a bug. I'll fix it today.
The library could try to use the internalURL by default. And if it cannot reach this endpoint it then could try to use the publicURL.
Do you agree?
Resolved issue #1. We need to make further tests.
Added some documentation to new configure function. Issue #1 resolved…
…. Diego, could you test it now again? Thanks!