request url of KVService is using related path instead of absolute path about kvision HOT 2 CLOSED

It's not a bug - it's a feature :-)

There are different cases. Sometimes it's like you said - you need to have your frontend on some complex url and the backend on plain /kv/foo. But there are other cases, when you need to have the frontend on some complex url and the backend on the same complex url as well. Its really hard to tell which case is more general - the first one is often used with history api routing, the other when using typical reverse-proxy configurations. Sometimes both are used at the same time.

That's why I had to chose reasonable default (relative path) and let all more complex cases (absolute paths) handle with kv_remote_url_prefix option.

from kvision.

OK

thank you for explaining it

I will close this issue

from kvision.