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

batch reporting via transactions.xml should have some initial validation

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • SaaS, 2.14.3 GA
    • Backend
    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      Currently our documentation for the transactions.xml endpoint states the following:

      Transactions from a single batch are reported only if all of them are valid. If there is an error in processing of at least one of them, none is reported.

      However, due to the nature of this request being asynchronous, the validation of this is not immediately returned.

      There is a desire to have some initial validation of the request and return an immediate non 20X response if the transactions are not valid syntactically. This will allow the application sending the API request to react and not invalidate the entire list of transactions.

      For example a missing app_id or user_key:

      [{
        "usage": {
          "hits": 1
        }
      }]
      

      OR

      [{
       "app_id": "",
        "usage": {
          "hits": 1
        }
      }]
      

      Both currently return a valid 202 response code.

      In addition, this could probably also validate the timestamps as they have a 24 hour deadline and this could avoid a similar issue there.

            Unassigned Unassigned
            rhn-support-spoole Shannon Poole
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: