I've encountered a possible issue/defect when using the Pagination function when connecting to a REST resource in the Copy Activity.
The Absolute Url parameter is expecting a jsonpath expression that points to either the Absolute URL or the Relative URL specified in the current response body that should provide the next set of results.
Absolute URL being the FQDN URI (eg. https://example.com/api/v1/service/ )
and Relative URL being just a path ( eg api/v1/service/ ).
I expect the system will distinguish the two, and if a relative URL is provided, it will be appended to the Base URL configured in the Linked Service.
I have a service which unfortunately adds a leading slash and skips the 'api' part of the path - eg. the value I get from the service is : "/v1/service/...<foo>"
However even with this erranous path, I expect that if I configure the Base URL in the Linked Service to be https://example.com/api , then the the system should append the "Absolute Url" parameter value to the Base URL in the Linked service. However it is not, it seems to not obeying the Base URL path configured in the Linked Service, what it seems to be doing is stripping away all of the the path from the original URI and then appends the Absolute Url value (eg. https://example.com/v1/service/ ) which of course will results in a 4xx error from the server.
It seems as if the system is not looking back at the Base URL on the Linked service, and instead is just looking at whatever URL was used in the original request and stripping away the whole path and re-writing it and I'm not so sure this is how it should behave as I think it should always refer back to the Base URL configuration of the Linked service.