Closed denopink closed 1 year ago
If we are to change this behavior (return a status code other than what is documented), we need to remember to update that page.
If memory serves, my conversation with Wes had us agreeing that anything between 520 and 599 (inclusive) would be usable by RDK, and that we can use that value directly in the Tridium response. We need to verify that this was communicated to RDK and that their implementations uses this range.
Yes, that's the right range (520-599 inclusive). Here is the code that produces the error codes for webpa: https://github.com/xmidt-org/wdmp-c/blob/317d79cadf2fd61031b7b553d5b5548c25d03f9d/src/wdmp_internal.h#L32
Tr1d1um panics when a device status code is either
100
or is an invalid http status code.Currently, we don't reuse the following device status codes as our response status code: 0, 500.
Related code: https://github.com/xmidt-org/tr1d1um/blob/ebd7188498832190b47a166e5ca7927d0baaf298/translation/transport.go#L213-L219
Our current documentation @ https://github.com/xmidt-org/xmidt/wiki/XMiDT-API states the following:
Questions: