How flexible is the URL to talk to form agents?

[Ongy]

Can the URL also contain PATH elements?

If not, is there an easy way to route the requests? E.g. by a unique enough header?
I guess worst case I could set a pseudo token as auth JWT and match on that instead of using it for auth?

[andydunstall]

Hi @Ongy, do you mind elaborating. I don't really understand the question

[Ongy]

Due to $reason I want to run piko on a port/hostname combination that already runs other HTTP based services.

Kubernetes ingress rules make this easy. There's various L7 attributes (path/header for the most part) that can be matched on to direct to the correct backend.
The question is whether the URL field (which provides hostname/port/protocol) is flexible enough to also provide a path prefix for the agent.
Or whether the header used for the authentication token JWT is unique enough (i.e. not Authorization: Bearer ...) to be matched on.

[andydunstall]

I still don't really understand

Are you referring to how to configure your Kubernetes ingress rule to route traffic to the Piko server?

[Ongy]

Yea, that's what I meant.

I tested it by now and saw that the paths used on the upgrade requests are sufficiently unique for my use.

[andydunstall]

ok great