non-root vhost exchanges and queues not showing via REST

[borogove]

In a test scenario with a fanout exchange and a single consumer queue, if I use the root vhost, I can hit the REST interface's /exchanges, /queues, and /bindings and get reasonable-looking results from each. If I create a vhost named "test" and use that, /bindings/test works ok:
curl -i http://172.16.200.99:9999/bindings/test
...
{"bindings":[{"queue":"consumer_recv","exchange":"","from_queue":"consumer_recv"},{"queue":"consumer_recv","exchange":"testroom","from_queue":"none"}]}

But /exchanges/test doesn't work at all:
curl -i http://172.16.200.99:9999/exchanges/test
...
{"error":"unhandled"}

And /queues/test produces this:
curl -i http://172.16.200.99:9999/queues/test
...
{"queues":[{}]}

Is the REST API supposed to give full access to bindings, queues, and exchanges in non-root vhosts? Is suffixing the vhost name the correct way to access them?