Unable to subscribe for Push style events using HTTP in the destination

[adathatri]

@edtanous @ratagupt

Clients cannot subscribe to Push style events using http in the destination.

Step to recreate:

Try to subscribe to Push style events using http in the destination.

}-bash-4.2$ curl -k -H "X-Auth-Token: $bmc_token" -X POST -D headers.txt https://${BMC_IP}/redfish/v1/EventService/Subscriptions -d '{"Destination" : "http://x.xx.xx.xx:xxxx/home/redfish/","Protocol":"Redfish", "RegistryPrefixes": ["Base","Task"]}'
{
  "Destination@Message.ExtendedInfo": [
    {
      "@odata.type": "#Message.v1_0_0.Message",
      "Message": "The value http://x.xx.xx.xx:xxxx/home/redfish/ for the property Destination is of a different format than the property can accept.",
      "MessageArgs": [
        "http://x.xx.xx.xx:xxxx/home/redfish/",
        "Destination"
      ],
      "MessageId": "Base.1.8.1.PropertyValueFormatError",
      "MessageSeverity": "Warning",
      "Resolution": "Correct the value for the property in the request body and resubmit the request if the operation failed."
    }
  ]

[edtanous]

There have been several fixes to event service subscriptions since you filed this. Can you please retest this on master and see if you still have the issue?

[adathatri]

I retested on latest master. I am still unable to subscribe using http in the destination.

[edtanous]

Is this still an issue?

[adathatri]

This is out of scope for my testing now. Hence closing this issue.