Closed c0c0n3 closed 8 months ago
Hi @c0c0n3 I tried the same with
$ curl -i https://kitt4sme.collab-cloud.eu/platform-configurator/kits
(no trailing slash) and it works fine.
It may be because the Platform Configurator handles the request /kits
, but not /kits/
. What do you think?
We're using FastAPI to serve the application, and the issue has been discussed here: https://github.com/tiangolo/fastapi/issues/2060.
This bug has been already fixed. However, with the new subdomain-based routing, both requests work (with and without the trailing slash).
Describe the bug
The Istio URL-path routing for Platform Configurator maps
/platform-configurator
to/
but it looks like this doesn't work at least for the/platform-configurator/kits
path which gets redirected to/kits
instead of/platform-configurator/kits/
.To Reproduce
Open a terminal and run
You should see the response contains a redirect to
http://kitt4sme.collab-cloud.eu/kits
If you look at the K8s logs, you should see Platform Configurator actually issues a redirect to
/kits
:Expected behavior
HTTP clients external to the mesh should be redirected to URLs starting with a path of
/platform-configurator/
, e.g./platform-configurator/kits
.Additional context
The above could be done e.g. by changing the Istio routing to
(notice there's no URL rewrite anymore) and then configuring the Platform Configurator Python app to serve URLs with a base path of
/platform-configurator
.