Tags: Dyalog/Jarvis
Tags
Revert changes in v.1.20.4 Simply checking the ⎕DR of the payload is insufficient. One needs to consider the content-type as well. As this has gotten more complicated, I'm reverting the changes made in v.1.20.4. REST mode endpoints will have to make sure their payloads are properly conditioned for transmission by Conga.
"Friendlier" treatment of non-JSON response payloads (#106) * "Friendlier" treatment of non-JSON response payloads Handles 2 and 4-byte character types, Classic characters, and 2-byte integers in the range 0-255. Otherwise, it's up to the user's endpoint code to properly encode a non-standard response payload. * Remove APLAN from test_ContentTypes Remove APLAN so that tests can be run on pre-20.0 versions of Dyalog
PreviousNext