value of next in the response when query filters are used should not contain JSON formatting
Bug #1793344 reported by
Mohammad S Khan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
High
|
Hardik Jasani |
Bug Description
when using query parameters with limit in most apis, the value of next contains JSON formatting. It should be reusable as is.
e.g. /v2/executions/
the next value returned is
8989/v2/
another case where 'in' is used with limit
8989/v2/
next response is
8989/v2/
Changed in mistral: | |
milestone: | none → stein-1 |
assignee: | nobody → Hardik Jasani (hjasani) |
Changed in mistral: | |
importance: | Undecided → High |
Changed in mistral: | |
status: | New → Confirmed |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/608677
Review: https:/