You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, as mentioned in Issue Add Support For Proxy Servers #12, the readme should mention that for authenticated proxies one must use Authenticator.setDefault() to set an Authenticator that will return the credentials required.
We need to support setting the root authority to something other than https://api.keen.io. Adding support for true HTTP proxying to query functionality and clearing up authenticated proxy support in the docs should/will be a separate issues. But, using an alternate base address is already supported for KeenClient via the setBaseUrl() method. It needs testing, and possibly work to make sure it applies to the KeenQueryClient as appropriate. This way a given client can leverage the custom SSL domains feature. This should work with HTTP proxying as well, of course.
No description provided.
The text was updated successfully, but these errors were encountered: