# The response format adds three optional fields: # - do_xlat If true, any values will be xlat expanded. Defaults to true. # - is_json If true, any nested JSON data will be copied to the attribute # in string form. Defaults to true. # - op Controls how the attribute is inserted into the target list. # Defaults to ':='. # { # "<attribute0>":{ # "is_json":<bool>, # "do_xlat":<bool>, # "op":"<operator>", # "value":[<value0>,<value1>,<valueN>] # }, # "<attribute1>":"value", # "<attributeN>":[<value0>,<value1>,<valueN>] # } This format cannot be received in the case Iam working on On Wed, 11 Aug 2021 at 19:48, Alan DeKok <aland@deployingradius.com> wrote:
On Aug 11, 2021, at 10:12 AM, Suneth Kariyawasam <sunethnk@gmail.com> wrote:
REST module works based on the HTTP response code and the response body needs to be in a specific format if I am not mistaken (Please correct me
if
I am wrong).
The response needs to be json.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html