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
The idea is to allow specifying a sub-path on the URL, so the client could work when an HTTP reverse proxy is routing the requests based on the path. For example, using a URL: https://example.com/influxdb/.
Apparently, this support was removed on version 2, as the flags no longer exists.
Is it possible to support this?
Thanks,
Yehoshua
The text was updated successfully, but these errors were encountered:
But it related to some generated code logic. So I can hardly help. Basically we pass the "host" as "https://example.com/influxdb/" and the path part should be conveyed to the final client config and it should work.
I'm opening a feature request for feature that was already done on 1.8: influxdata/influxdb#10294
It was done by @bthesorceror on influxdata/influxdb#16599.
The idea is to allow specifying a sub-path on the URL, so the client could work when an HTTP reverse proxy is routing the requests based on the path. For example, using a URL:
https://example.com/influxdb/
.Apparently, this support was removed on version 2, as the flags no longer exists.
Is it possible to support this?
Thanks,
Yehoshua
The text was updated successfully, but these errors were encountered: