Hi Jeff,i
I'm retired and don't check this forum frequently, but I don't seem to be able to help myself to chime in every once and a while :-) . I would suggest you open a PMR on this one. From your description, it would appear your operation path is simply /User but what is being returned by the variable $(api.operation.path) is incorrectly including the inbound request url query string. I'd think the variable should simply resolve to /User. $(request.search) is properly resolving to the search string including the question mark.
Best Regards,
Steve Linn
------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM Retired
------------------------------
Original Message:
Sent: Fri September 05, 2025 10:52 AM
From: Jeff Bennett
Subject: target-url question
I have a target-url configured like: target-url: $(some-value)/user-api$(api.operation.path)$(request.search)
There is a parameter passed to this of: includeClientProfile=true
The url is resolving to: https://api.<some-value>.com/user-api/User?includeClientProfile=true?includeClientProfile=true
My question is.. why would the query parm value double up at this point? This was working in v5 compatible, but after we've migrated to v10 we're seeing this issue (which is causing a 400 Bad Request) from the backend.
------------------------------
Jeff Bennett
------------------------------