/v1.1 returns a 500, /v1.1/ gives desired respons
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Alex Meade |
Bug Description
$ curl -H"X-Auth-Token: --yourkey--" http://
{"ver...
$ curl -H"X-Auth-Token: --yourkey--" http://
{"cloudServersF
It produced this exception in the api:
2011-10-03 18:08:37,089 ERROR nova.api.openstack [-] Caught error: URL or environ must be provided
Traceback (most recent call last):
File "/home/
return req.get_
File "/usr/local/
application, catch_exc_
File "/usr/local/
app_iter = application(
File "/usr/local/
return resp(environ, start_response)
File "/usr/local/
return resp(environ, start_response)
File "/usr/local/
return resp(environ, start_response)
File "/usr/local/
config.environ = environ
File "/usr/local/
self.
File "/usr/local/
result = mapper.
File "/usr/local/
raise RoutesException
Changed in nova: | |
assignee: | nobody → Alex Meade (alex-meade) |
status: | New → In Progress |
Changed in nova: | |
milestone: | none → essex-1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-1 → 2012.1 |
"Version request URLs should always end with a trailing slash (/). If the slash is omitted, the server may respond with a 302 redirection request." -- The current v1.1 spec
So the real bug is that it should be a 302 response, not a 500 error