Pulp

Issue #3502

Updated by daviddavis over 6 years ago

<pre> 
 $ http http://localhost:8000/api/v3/repositories/e2bf7dc1-8638-420f-be13-1c60e660249f/versions/ 
 HTTP/1.0 400 Bad Request 
 Allow: GET, POST, HEAD, OPTIONS 
 Content-Length: 40 
 Content-Type: application/json 
 Date: Mon, 19 Mar 2018 16:17:00 GMT 
 Server: WSGIServer/0.2 CPython/3.5.4 
 Vary: Accept, Cookie 
 X-Frame-Options: SAMEORIGIN 

 [ 
     "No value supplied for content filter" 
 ] 
 </pre> 

 Bug was created in this PR: 

 https://github.com/pulp/pulp/pull/3373/files#diff-3072a203aa1fcb7d2fc8af1885d4d6ceR144 

 The problem is that I tried to make <code>http http://localhost:8000/api/v3/repositories/e2bf7dc1-8638-420f-be13-1c60e660249f/versions/?content=</code> return a 400 error but it also affected requests where no <code>content</code> filter is supplied. See the tasks endpoint as an example: 

 <pre> 
 $ http http://localhost:8000/api/v3/tasks/ 
 HTTP/1.0 200 OK 
 Allow: GET, HEAD, OPTIONS 
 Content-Length: 5365 
 Content-Type: application/json 
 Date: Mon, 19 Mar 2018 16:18:35 GMT 
 Server: WSGIServer/0.2 CPython/3.5.4 
 Vary: Accept, Cookie 
 X-Frame-Options: SAMEORIGIN 


 $ http http://localhost:8000/api/v3/tasks/?worker=                                                                                                                                      
                                                                                                                                       [49/1852] 
 HTTP/1.0 400 Bad Request 
 Allow: GET, HEAD, OPTIONS 
 Content-Length: 40 
 Content-Type: application/json 
 Date: Mon, 19 Mar 2018 16:17:54 GMT 
 Server: WSGIServer/0.2 CPython/3.5.4 
 Vary: Accept, Cookie 
 X-Frame-Options: SAMEORIGIN 

 [ 
     "No value supplied for worker filter." 
 ] 
 </pre> </code> 

 No idea why these filters are behaving differently.

Back