Support of "&" in BaseURLs
"&" can be used in access info as defined in services and subscriptions. It is tested and works fine. The requirement is to support query strings in the BaseURL.
Ampersands are already supported. In technical service descriptor file it has to be escapted and written as "& a m p ;" (without spaces) On the other end service can retrieve parameters send by URL.
I got information that the issue still exists in 16.1.4. Remaining issue is not about escape handling and importing technical services, but using services in the marketplace portal, having a BaseURL with a query string. Such as 'http://example.com/?a=foo&b=bar'.
@DawidCh Please check the "use service" button on the marketplace subscription.
@DawidCh Please wait. I'll take this.
@GoebelL is it still in progress or I can move it back to new issues?
Thanks for reminding. There is some more light on the cause, but no solution yet. It turned out that this request is not that trivial. In fact, technical service import and marketplace portal handling are both complete and correct. However, the remaining issue resides on the portal reverse proxy, which doesn't support for rewriting query strings from subscription base URLs. For details, have a look to AdmServer and AdmRule. URL from requested subscription is obtained from session cache in 77, but only the path substring is applied to rewrite and revert patters (Line 95 and 104). Rest of URL is excluded.
Please check.