Uploaded image for project: 'ui-eholdings'
  1. ui-eholdings
  2. UIEH-497

mod-kb-ebsco - consistent use of HTTP 400 vs 422 status code

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Won't Do
    • None
    • 1.3.0
    • Spitfire

    Description

      While writing API tests for mod-kb-ebsco we found some inconsistency in when HTTP status code 422 is used vs HTTP status code 400.

      For example
      POST /eholdings/titles with an invalid name returns an HTTP status code 422
      PUT /eholdings/resources with an invalid name returns an HTTP status code 400

      This could be due to returning error information as a passthrough from rm api vs directly detecting the error in mod-kb-ebsco.

      Would be helpful to review status codes that are returned to be sure they are consistent and predictable.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                cgodfrey Carole Godfrey
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases