Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-69

Apicast management API: Validation of JSON

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.0 ER4
    • 2.0 ER3
    • Gateway
    • None

      Apicast management API is not validating any JSON, sent through `POST` request.
      Malformed JSON may even cause that gateway will crash and not recover.

      When non valid config JSON has been send: there will be no error message admin, but instead ok message.

      for example:

      Crash:

      asdsadsadsadaa
      

      ��

      Also when you send in configuration file two different versions of the same api, the second one configuration will apply -> I would suggest that this should be also validated and return error, to user is not confused.

      Also it gave us some time to realize, that we have to send the specific configuration that we downloaded from admin portal through UI, not just by pasting json, but formatted it this way:

      {
        services: [
           <CONTENT_OF_SPECIFIC_VERSION>
        ]
      }
      

      When we just send only that content of the file, it responded ok, but configuration wasn't changed. (We know how to solve this problem but OK message is confusing.)

              mcichra Michal Cichra (Inactive)
              pstanko@redhat.com Peter Stanko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: