You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of ConsumerAssetRequestController for fetching data automatically with
cached EDR, for now supports only the request using the endpointUrl which should point to the
asset location on the provider side ProviderGatewayController. This requires users to know the
URL of the proxied asset on the provider side, which in some case cannot be known. For those situation
we could use directly the EDRendpointUrl for fetching data.
In case of the AssetRequest does not contain the endpointUrl we should fallback to the one provided in the cached EDR and we also should be able to support additional path segment and query parameters for this use case.
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
The current implementation of
ConsumerAssetRequestController
for fetching data automatically withcached EDR, for now supports only the request using the
endpointUrl
which should point to theasset location on the provider side
ProviderGatewayController
. This requires users to know theURL of the proxied asset on the provider side, which in some case cannot be known. For those situation
we could use directly the
EDR
endpointUrl
for fetching data.In case of the
AssetRequest
does not contain theendpointUrl
we should fallback to the one provided in the cachedEDR
and we also should be able to support additionalpath
segment and query parameters for this use case.The text was updated successfully, but these errors were encountered: