Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

When CQL is rejected, the resulting 400 Bad Request contains no information

Description

Submitting a query like key=="dbinfo" to mod-settings results in rejection — seeingly because of the double quotes around the query term, see — but the problem with parsing is not communicated to the client. The WSAPI request is rejected with HTTP status 400 Bad Request, but there is no meaningful additional information in the content of the response — only a restatement of the "400 Bad Request" formatted in HTML.

To reproduce:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Charlotte WhittNovember 20, 2023 at 5:26 PM

No worries

Mike TaylorNovember 18, 2023 at 10:08 AM

Haha, that was total nonsense! I was sending to query to /ldp/config, not /settings/entries! That means the problems were in mod-ldp, not mod-settings — and mod-ldp does not even claim to support CQL!

I will close this issues as invalid. Sorry to have wasted everyone’s time.

Won't Do

Details

Assignee

Reporter

Priority

Development Team

None

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 18, 2023 at 9:11 AM
Updated November 20, 2023 at 5:26 PM
Resolved November 18, 2023 at 10:08 AM
TestRail: Cases
TestRail: Runs