action #65702
coordination #36712: [saga] Use YaST specific framework for GUI testing
coordination #50672: [funtional][y][epic] Use libyui-rest-api for YaST modules testing
[functional][y] 200 HTTP response status code is returned even though invalid filter type is used
0%
Description
libyui-rest-api returns 200 HTTP response status code, when sending request with the invalid/unsupported filter type (Other than id, label, type).
Steps to reproduce:
- Run any app with libyu-rest-api (e.g.
xdg-su -c "env YUI_HTTP_PORT=9999 /sbin/yast2 timezone"); - Send GET request with wrong filter type (e.g.
curl -s -o /dev/null -w "%{http_code}" http://localhost:9999/v1/widgets?idzzz=manuals). - Note the response code.
Expected result:
404 or other error response code is returned.
Actual result:
200 (Success) response code is returned.
History
#1
Updated by riafarov almost 3 years ago
Updated by - Target version set to future
#2
Updated by riafarov almost 3 years ago
As per our discussion, there is no good reason to add such check now. However, I've added it to POST request in case no search criteria is provided.
#3
Updated by riafarov over 2 years ago
- Project changed from openQA Tests to qe-yam
#4
Updated by okurz over 1 year ago
Updated by - Priority changed from Normal to Low
This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. The ticket will be set to the next lower priority of "Low" as discussed with qe-yast PO oorlov (https://suse.slack.com/archives/C02LECV2R0X/p1636974668013200)