How does pathSegments work during a PUSH transfer?

[Arthur380]

Hello,

I'm encountering an error when attempting an HttpData-PUSH transfer with a pathSegments.

First, here is the payload I use to create my asset:

{
 "@context": {
   "@vocab": " https://w3id.org/edc/v0.0.1/ns/"
 },
 "@id": "assetId",
 "properties": {
   "name": "product description",
   "contenttype": "application/json"
 },
 "dataAddress": {
   "type": "HttpData",
   "name": "Test asset",
   "baseUrl": " http://localhost:8084/",
   "proxyPath": "true",
   "proxyMethod": "true"
 }
}

Then, I create a policy, a contract definition, I query the catalog to retrieve the @id of odrl:hasPolicy, then I negotiate the contract and retrieve the contract agreement ID. Then I perform a PUSH transfer with the following payload:

{
 "@context": {
   "@vocab": " https://w3id.org/edc/v0.0.1/ns/"
 },
 "@type": "TransferRequestDto",
 "connectorId": "provider",
 "counterPartyAddress": " http://localhost:19194/protocol",
 "contractId": "8d1c59e7-d7ec-4005-9136-b7867b38b325",
 "protocol": "dataspace-protocol-http",
 "transferType": "HttpData-PUSH",
 "dataDestination": {
   "type": "HttpData",
   "baseUrl": " https://webhook.site/3b74feb3-97b2-4034-8943-9c4906674dea"
 },
 "privateProperties": {
   "pathSegments": "test",
   "method": "GET",
   "contentType": "application/json",
   "mediaType": "application/json"
 }
}

However, in the Provider connector's logs, I see the following error:

No source was found for DataFlow 'bc9018c9-72f0-4bc3-9900-91dc7b05306d'. This may indicate an inconsistent state.

If I specify the full endpoint in the baseUrl when creating the asset, the transfer request works fine.

So my question is: how can I use pathSegments in a transfer request while only specifying the base address and port in the baseUrl when creating the asset?
My goal is to query the URL http://localhost:8084/test and http://localhost:8084/test2 by using an asset with a base URL http://localhost:8084/ .

Also, if I perform a PULL transfer and retrieve the authorization from the EDR, I don't understand why I need to query the provider connector from my consumer application to fetch the data. Wouldn't it be more logical to address the consumer connector instead ?
When I query the consumer connector, I get the following error: "AccessTokenData with ID 'c9366a4e-944a-4c43-9b3a-b578790ebc16' does not exist."

Thanks in advance for your help!