Bad request response served with 200 status code on metadata delete
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
The '{ d }' considered as an invalid key by the nova, but the HTTP status code is 200, in the response.
tempest.
tempest.
tempest.
tempest.
<title>Error response</title>
</head>
<body>
<h1>Error response</h1>
<p>Error code 400.
<p>Message: Bad request syntax ('DELETE /v2/50b11029b6d
<p>Error code explanation: 400 = Bad request syntax or unsupported method.
</body>
You can modify tempest.
I also wonder is HTML response format the default ?
Changed in nova: | |
assignee: | nobody → lizheming (lizheming-li) |
Changed in nova: | |
assignee: | lizheming (lizheming-li) → nobody |
Changed in nova: | |
assignee: | nobody → Kent Wang (k.wang) |
Changed in nova: | |
status: | Triaged → Won't Fix |
assignee: | Kent Wang (k.wang) → nobody |
so the issue is spaces in the request is rejected by our http server before it ever gets into our wsgi stack.