On Sep 4, 2019, at 9:31 AM, Emmett Cox <emmett.cox@...> wrote:

Hi Luis,

I was looking into writing some csit tests for the new use case of invoking actions in json.

We found through testing that invoking actions through xml and json will work , however when writing the csit tests we found that the trying to invoke json will fail with a 415 error, like in the attached screenshot.

Through a bit of rooting we found that the content-type header seems to be causing the error, on account of the TemplatedRequests.Post_As_Json_Templated method using the header application/yang.data+json, rather than application/json - and when we test the actions using yang.data+json it will receive the same error.

I was wondering why this header is used, rather than application/json as part of these requests, and how do the existing use cases work with these headers?

Regards,

Emmett

<Screenshot from 2019-09-04 16-45-43.png>

On Sep 6, 2019, at 10:51 PM, Robert Varga <nite@...> wrote:

On 06/09/2019 22:09, Luis Gomez wrote:

Hi Emmett,

I pulled this thread from the mail archives on how to use the REST
headers in robot FW, I hope it helps:

https://lists.opendaylight.org/pipermail/integration-dev/2016-January/005551.html

Yeah, that link is gone. Casey, what is the story about Groups.io archives?

I mean getting a plain 404 is going to be a *ton* of pain for all the
links we have ever posted.

Unless it is literally impossible to get the message links redirect
property, can we at least keep the old archive in read-only mode?

As it currently stands, I have *nothing* to go on to try to find the
message Luis referenced.

Thanks,
Robert