any idea how to solve it? I'm having the same problem (my ksqldb server runs behind an ingress controller)

Hi, seems the client should be refactored to support this. The code seems not complicatedtk provide a PR. Curious, why its not implemented yet, maybe there some hidden complexity behind this ?

Not familiar with the code, but I assume it's just a random bug.

I'm facing the same issue, but from what I understand the bug is not in the client, it's in the server - when you have it behind ingress you need to make it aware of the "/test/" part of url, but as far as i know there is no configuration parameter for passing this path. Or is there a one?

I'm considering using nginx reverse proxy to work around this.
I assume that to really fix it on sever side would require one of:

a. adding "contextPath" parameter to server configuration to make it generate links and redirects correctly

b. eliminating HTTP redirect which is now what welcomes you at root endpoint:

• Mark bundle as not supporting multiuse
  < HTTP/1.1 307 Temporary Redirect
  < location: /info
  < content-length: 0

Why not returning the info here, instead of having separate /info path?

This is an issue around how KsqlTarget is instantiated. Throughout initialization the full server name with path is present, but when the client is instantiated it only uses the host. I can create a PR for this and a test container can be found here boriscosic/ksqldb-cli.