Issue #797
closed
Wrong message error during query content applicability request
Description
$ curl -i -H "Accept: application/json" -H "WebFrameworkSwitch: webpy" -X POST -k -u admin:admin -d '{}' "https://localhost/pulp/api/v2/consumers/content/applicability/"
HTTP/1.1 400 Bad Request
Date: Wed, 18 Mar 2015 17:26:17 GMT
Server: Apache/2.4.10 (Fedora) OpenSSL/1.0.1e-fips mod_wsgi/3.5 Python/2.7.5
Content-Length: 34
Connection: close
Content-Type: application/json
"Invalid properties: ['criteria']"
I expect:
$ curl -i -H "Accept: application/json" -H "WebFrameworkSwitch: django" -X POST -k -u admin:admin -d '{}' "https://localhost/pulp/api/v2/consumers/content/applicability/"
HTTP/1.1 400 BAD REQUEST
Date: Wed, 18 Mar 2015 17:26:35 GMT
Server: Apache/2.4.10 (Fedora) OpenSSL/1.0.1e-fips mod_wsgi/3.5 Python/2.7.5
Content-Length: 93
Connection: close
Content-Type: text/html; charset=utf-8
Invalid properties: ["The input to this method must be a JSON object with a 'criteria' key."]
Updated by ipanova@redhat.com almost 10 years ago
- Status changed from NEW to POST
Updated by ipanova@redhat.com almost 10 years ago
- Status changed from POST to MODIFIED
Updated by dkliban@redhat.com over 9 years ago
- Status changed from MODIFIED to 5
Updated by igulina@redhat.com over 9 years ago
- Status changed from 5 to 6
>> rpm -qa pulp-server
pulp-server-2.7.0-0.4.beta.el7.noarch
>> curl -i -H "Accept: application/json" -H "WebFrameworkSwitch: webpy" -X POST -k -u admin:admin -d '{}' "https://localhost/pulp/api/v2/consumers/content/applicability/"
HTTP/1.1 400 BAD REQUEST
Date: Wed, 15 Jul 2015 12:43:42 GMT
Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.1e-fips mod_wsgi/3.4 Python/2.7.5
Content-Length: 93
Connection: close
Content-Type: text/html; charset=utf-8
Invalid properties: ["The input to this method must be a JSON object with a 'criteria' key."]
Updated by amacdona@redhat.com about 9 years ago
- Status changed from 6 to CLOSED - CURRENTRELEASE
Updated by bmbouter over 4 years ago
- Category deleted (
14)
We are removing the 'API' category per open floor discussion June 16, 2020.
.