[openstack-dev] Keystone Service Catalog endpoints vs. API versions

Jay Pipes jaypipes at gmail.com
Wed May 1 17:08:47 UTC 2013


On 04/30/2013 09:09 PM, Gabriel Hurley wrote:
> 6: (about project ids in urls) The argument in favor of them (passed to
> me by some of the original Nova devs) is that by the strictest
> definition, to be RESTful an API can’t change its URL structure based on
> context, so any context which can alter the response has to go in the
> URL. Personally I think this is an impractical requirement and most
> modern RESTful APIs have completely thrown out this notion. I’m 100% in
> favor of eliminating the practice in OpenStack, but it would require a
> significant deprecation process. In the meantime I think the clients
> should know if a project ID belongs in the URL and should be capable of
> constructing those URLs themselves from the root service endpoint
> contained in the catalog.

+1

Use a Vary: X-Tenant-Id HTTP header instead of polluting the URI with
the tenant ID.

Oh, sorry, I meant X-Project-Id, since the term tenant has magically
disappeared now.

-jay



More information about the OpenStack-dev mailing list