Http declarative client not taking the url specified from config when query parameters are involved

[srinunagulapalli]

We have observed that, when we are using a declarative client that has query parameters, the url path for the service specified in the config for url is taking into account the substring only till the second / and not the full url path specified while this is taking in the full url path when there are no query parameters involved.

In the cases where it is not taking the full url path, we had to break the url path specified in the url to url and path having the values of the host and context path respectively for it to form the full url.

Can you please let us know when we can use the full url path in the url in the config and when we have to break it into url and path if this is the expected behavior?

[yawkat]

Can you show an example

[srinunagulapalli]

You can refer to this repository clienturldemo.
Please refer to README for reproducing the issue