Detail page uri in payload instead of encoded in request url?

[Ceetto]

We ran into an issue when using apache as a load balancer.
When opening a detail page sampo sends a request to api_url/perspective/page/uri, however since that uri contains encoded slashes some web servers, like apache, will block the request and return a 404 without it ever even getting to sampo.

A solution is of course to configure apache to let such requests pass, however passing encoded uris in the request url could still cause errors with other load balancers or proxies.

A solution on the sampo side would be to pass the uri in a payload instead of in the url. Could this potentially be a problem in some cases or do you think this is a good idea?

@annasahola @HeikkiR

[HeikkiR]

I think you mean api call from client side to the backend in the fetchByURIEpic. I think you could try making changes to the api to pass the uri in payload. I don't think there would be issues.

[Ceetto]

That is indeed what I meant. I made the change and it seems to work perfectly.