Uploaded image for project: 'Magnolia REST Framework'
  1. Magnolia REST Framework
  2. MGNLREST-79

Provide error messages for REST calls that return a client error message

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 2.2.12
    • 1.1.1
    • services
    • None
    • DevX 4
    • 3

      Currently for instance PUT calls to /.rest/workspace/path return 400 Bad Request for all of the following error conditions:

      • No name specified for node to create
      • No type specified for node to create
      • Parent path does not exist
      • The request doesn't contain any nodes to create
      • The path to create already exists

      However, a client can't differentiate between these conditions and display a meaningful error message, because all that is returned is a 400 Bad Request. I'd like to suggest returning an error message when an error is sent, which will make it easier to troubleshoot calls that return an error status code and also will allow client builders to provide a better experience by being able to show a specific error message to the user when something doesn't work.

        Acceptance criteria

              chuong.doan Chuong Doan Huy
              breun Nils Breunese
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 2d 2.5h
                    2d 2.5h