POSTMAN 6. Get EndpointDataReference Error 404 Not Found #300

dimitriskranias · 2024-07-18T10:19:16Z

dimitriskranias
Jul 18, 2024

Hello everyone,

When executing the POST request described in Step 6 of Executing REST requests using Postman I get the following response:

<html>

<head>
    <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1" />
    <title>Error 404 Not Found</title>
</head>

<body>
    <h2>HTTP ERROR 404 Not Found</h2>
    <table>
        <tr>
            <th>URI:</th>
            <td>/api/management/v3/edrs/request</td>
        </tr>
        <tr>
            <th>STATUS:</th>
            <td>404</td>
        </tr>
        <tr>
            <th>MESSAGE:</th>
            <td>Not Found</td>
        </tr>
        <tr>
            <th>SERVLET:</th>
            <td>EDC-management</td>
        </tr>
    </table>

</body>

</html>

I am hitting the following endpoint: {{HOST_CATALOG_SERVER}}/api/management/v3/edrs/request where {{HOST_CATALOG_SERVER}} is http://127.0.0.1/provider-catalog-server/cp

In all the previous steps I am getting the correct outputs, as indicated in the README.md
e.g. in Step 5 when hitting {{HOST_CATALOG_SERVER}}/api/management/v3/transferprocesses/request, I am getting the following response:

[
    {
        "@id": "dd5afbfc-cbb1-4264-949d-b60933bf03f6",
        "@type": "TransferProcess",
        "state": "STARTED",
        "stateTimestamp": 1721295872217,
        "type": "CONSUMER",
        "callbackAddresses": [],
        "correlationId": "c85fb28e-7d33-4e1e-a800-4547a9a872c9",
        "assetId": "asset-1",
        "contractId": "3af25892-2161-419e-b48a-7d4639d3eaf6",
        "transferType": "HttpData-PULL",
        "dataDestination": {
            "@type": "DataAddress",
            "type": "HttpProxy"
        },
        "@context": {
            "@vocab": "https://w3id.org/edc/v0.0.1/ns/",
            "edc": "https://w3id.org/edc/v0.0.1/ns/",
            "odrl": "http://www.w3.org/ns/odrl/2/"
        }
    },
    {
        "@id": "5ee5ac84-a638-4985-8ab0-47ef32f4665d",
        "@type": "TransferProcess",
        "state": "STARTED",
        "stateTimestamp": 1721293011947,
        "type": "CONSUMER",
        "callbackAddresses": [],
        "correlationId": "87519894-663c-46bb-af47-f8734e701b5d",
        "assetId": "asset-1",
        "contractId": "5b904c9d-6a04-4545-b88e-affc73f95b77",
        "transferType": "HttpData-PULL",
        "dataDestination": {
            "@type": "DataAddress",
            "type": "HttpProxy"
        },
        "@context": {
            "@vocab": "https://w3id.org/edc/v0.0.1/ns/",
            "edc": "https://w3id.org/edc/v0.0.1/ns/",
            "odrl": "http://www.w3.org/ns/odrl/2/"
        }
    }
]

Is anyone familiar as to why the Error 404 Not Found is occurring? (Is it possibly an omittion on my part, e.g in the endpoint? Because the body doesn't have any variables that could go wrong)

paullatzelsperger · 2024-07-18T10:21:05Z

paullatzelsperger
Jul 18, 2024
Collaborator

did you replace the ID in the request path of the "Get EDR DataAddress for TransferId" request with the actual EDR id, so either dd5afbfc-cbb1-4264-949d-b60933bf03f6 or 5ee5ac84-a638-4985-8ab0-47ef32f4665d

4 replies

dimitriskranias Jul 18, 2024
Author

I did but this happens with both Transfer Process ID's:

<html>

<head>
    <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1" />
    <title>Error 404 Not Found</title>
</head>

<body>
    <h2>HTTP ERROR 404 Not Found</h2>
    <table>
        <tr>
            <th>URI:</th>
            <td>/api/management/v3/edrs/dd5afbfc-cbb1-4264-949d-b60933bf03f6/dataaddress</td>
        </tr>
        <tr>
            <th>STATUS:</th>
            <td>404</td>
        </tr>
        <tr>
            <th>MESSAGE:</th>
            <td>Not Found</td>
        </tr>
        <tr>
            <th>SERVLET:</th>
            <td>EDC-management</td>
        </tr>
    </table>

</body>

</html>

I'll try running the whole process from the start (meaning the whole deployment), and I will come back to this discussion if this error persists

paullatzelsperger Jul 18, 2024
Collaborator

you can always try to get all EDRs first, i.e. /api/management/v3/edrs/request

dimitriskranias Jul 18, 2024
Author

Thats what I initially tried (as stated in my initial question) but still i get similar error response. The api/management/v3/edrs endpoints seem to be the only ones that can't be found for some reason. I'll try again with the latest SNAPSHOT version, maybe it was something that was fixed, and come back to you. (I was using an older 0.8.1-SNAPSHOT when i built it) If the problem persists I'll also try the STABLE version 0.8.0.
Thanks for the assistance though!

dimitriskranias Jul 18, 2024
Author

I have tested both with the latest SNAPSHOT version and with 0.8.0 but the same error happens. I haven't bumped into a problem with any of the other endpoints (that are used in this Tutorial).

So, a brief recap:

I am hitting http://127.0.0.1/provider-catalog-server/cp/api/management/v3/transferprocesses/request and the output is:

[
    {
        "@id": "79c9a796-9df9-4d37-9d54-e06e110352e9",
        "@type": "TransferProcess",
        "state": "STARTED",
        "stateTimestamp": 1721306302524,
        "type": "CONSUMER",
        "callbackAddresses": [],
        "correlationId": "7b5792c3-7537-48ab-9c67-884a8d383856",
        "assetId": "asset-1",
        "contractId": "5fd55eac-2175-4867-ad85-87f45ee3baa9",
        "transferType": "HttpData-PULL",
        "dataDestination": {
            "@type": "DataAddress",
            "type": "HttpProxy"
        },
        "@context": {
            "@vocab": "https://w3id.org/edc/v0.0.1/ns/",
            "edc": "https://w3id.org/edc/v0.0.1/ns/",
            "odrl": "http://www.w3.org/ns/odrl/2/"
        }
    }
]

I request from http://127.0.0.1/provider-catalog-server/cp/api/management/v3/edrs/request and the response is 404:

<html>

<head>
    <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1" />
    <title>Error 404 Not Found</title>
</head>

<body>
    <h2>HTTP ERROR 404 Not Found</h2>
    <table>
        <tr>
            <th>URI:</th>
            <td>/api/management/v3/edrs/request</td>
        </tr>
        <tr>
            <th>STATUS:</th>
            <td>404</td>
        </tr>
        <tr>
            <th>MESSAGE:</th>
            <td>Not Found</td>
        </tr>
        <tr>
            <th>SERVLET:</th>
            <td>EDC-management</td>
        </tr>
    </table>

</body>

</html>

I also use the GET request http://127.0.0.1/provider-catalog-server/cp/api/management/v3/edrs/79c9a796-9df9-4d37-9d54-e06e110352e9/dataaddress and I get a similar response:

<html>

<head>
    <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1" />
    <title>Error 404 Not Found</title>
</head>

<body>
    <h2>HTTP ERROR 404 Not Found</h2>
    <table>
        <tr>
            <th>URI:</th>
            <td>/api/management/v3/edrs/79c9a796-9df9-4d37-9d54-e06e110352e9/dataaddress</td>
        </tr>
        <tr>
            <th>STATUS:</th>
            <td>404</td>
        </tr>
        <tr>
            <th>MESSAGE:</th>
            <td>Not Found</td>
        </tr>
        <tr>
            <th>SERVLET:</th>
            <td>EDC-management</td>
        </tr>
    </table>

</body>

</html>

It seems peculiar to me that the only API endpoints that aren't found (because even the last request http://127.0.0.1/provider-qna/public/api/public returns a non 404 error) are these 2 (the ones associated with EDR).
Could you possibly propose a way to investigate the reason that they are not found? Because I followed all the deployment steps you provided. My run environment is WSL2, if it helps.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

POSTMAN 6. Get EndpointDataReference Error 404 Not Found #300

{{title}}

Replies: 1 comment 4 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

POSTMAN 6. Get EndpointDataReference Error 404 Not Found #300

dimitriskranias Jul 18, 2024

Replies: 1 comment · 4 replies

paullatzelsperger Jul 18, 2024 Collaborator

dimitriskranias Jul 18, 2024 Author

paullatzelsperger Jul 18, 2024 Collaborator

dimitriskranias Jul 18, 2024 Author

dimitriskranias Jul 18, 2024 Author

dimitriskranias
Jul 18, 2024

Replies: 1 comment 4 replies

paullatzelsperger
Jul 18, 2024
Collaborator

dimitriskranias Jul 18, 2024
Author

paullatzelsperger Jul 18, 2024
Collaborator

dimitriskranias Jul 18, 2024
Author

dimitriskranias Jul 18, 2024
Author