tree 0a63d97668c7c8c1e9f365b6029526e5ca4acbdb
parent 9f03894ecf12e0d0ffb0ba7855c256f33f959e44
author Abiola Asojo <abiola.asojo@ibm.com> 1742315371 +0000
committer Ed Tanous <ed@tanous.net> 1742481564 +0000

Fix getting a response for wrong URI

Resolve getting a response for wrong URI in Update Service
URI (/redfish/v1/UpdateService/FirmwareInventory/)

- After the fix a wrong URI that partially matches the
  last characters in a valid URI now gets a 404 as shown
  in the example below :

$ curl -k -H "X-Auth-Token: $bmc_token" -X GET
https://$bmc/redfish/v1/UpdateService/FirmwareInventory/5e
{
  "error": {
    "@Message.ExtendedInfo": [
      {
        "@odata.type": "#Message.v1_1_1.Message",
        "Message": "The resource at the URI '/redfish/v1/
        UpdateService/FirmwareInventory/5e' was not found.",
        "MessageArgs": [
          "/redfish/v1/UpdateService/FirmwareInventory/5e"
        ],
        "MessageId": "Base.1.19.ResourceMissingAtURI",
        "MessageSeverity": "Critical",
        "Resolution": "Place a valid resource at the URI or
        correct the URI and resubmit the request."
      }
    ],
    "code": "Base.1.19.ResourceMissingAtURI",
    "message": "The resource at the URI '/redfish/v1/
    UpdateService/FirmwareInventory/5e' was not found."
  }

- Two common errors were fixed with the changes
  - imprecise-matching
  - not-responding-to-404

- The fix also includes changes to the software images to
  only look under /xyz/openbmc_project/software/.

Tested: No longer getting a response for wrong URI in Update
Service URI.

Change-Id: I72d8452b8ca1ef095d093a57bc14fade380be617
Signed-off-by: Abiola Asojo <abiola.asojo@ibm.com>