Bug in x-object-manifest value handling
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Invalid
|
Medium
|
Unassigned | ||
Diablo |
Invalid
|
Medium
|
Unassigned |
Bug Description
There is not enough (or any?) x-object-manifest value validation:
curl -ik -H "X-Auth-Token: token" https:/
HTTP/1.1 200 OK
Last-Modified: Wed, 20 Apr 2011 19:52:44 GMT
Etag: e19c1283c925b32
Content-Length: 15
Content-Type: application/
Date: Wed, 20 Apr 2011 19:53:12 GMT
this is a test
curl -ik -H "X-Auth-Token: token" -H "X-Object-Manifest: stuff" -X POST https:/
HTTP/1.1 202 Accepted
Content-Length: 159
Content-Type: text/html; charset=UTF-8
Date: Wed, 20 Apr 2011 19:55:30 GMT
<html>
<head>
<title>202 Accepted</title>
</head>
<body>
<h1>202 Accepted</h1>
The request is accepted for processing.<br /><br />
</body>
</html>
curl -ik -H "X-Auth-Token: token" https:/
HTTP/1.1 500 Internal Server Error
Content-Type: text/html; charset=UTF-8
Date: Wed, 20 Apr 2011 19:56:00 GMT
Connection: close
Content-Length: 228
<html>
<head>
<title>500 Internal Server Error</title>
</head>
<body>
<h1>500 Internal Server Error</h1>
The server has either erred or is incapable of performing the requested operation.<br /><br />
</body>
</html>
Changed in swift: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in swift: | |
status: | Confirmed → Invalid |
This no longer happens.