From e9646a4419db5e6a963bb34f05896be6b8642dc9 Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Thu, 21 Jan 2016 10:43:43 -0500 Subject: [PATCH] remove docs about format extensions The format extensions concept (adding .json / .xml) is no longer really a thing. The router supports it, but we only have json responses, so there is no reason to advertise it. Change-Id: I07ba13a98ce55c215c6b676b5ff41d7d60babfde --- api-guide/source/versions.rst | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/api-guide/source/versions.rst b/api-guide/source/versions.rst index 9ca2feeae786..4685695c37a9 100644 --- a/api-guide/source/versions.rst +++ b/api-guide/source/versions.rst @@ -102,13 +102,7 @@ You can also obtain additional information about a specific version by performing a **GET** on the base version URL (such as, ``https://servers.api.openstack.org/v2.1/``). Version request URLs must always end with a trailing slash (``/``). If you omit the slash, the -server might respond with a 302 redirection request. Format extensions -can be placed after the slash (such as, -``https://servers.api.openstack.org/v2.1/.json``). - -.. note:: This special case does not hold true for other API requests. In - general, requests such as ``/servers.json`` and ``/servers/.json`` are - handled equivalently. +server might respond with a 302 redirection request. For examples of the list versions and get version details requests and responses, see `*API versions* @@ -118,4 +112,3 @@ The detailed version response contains pointers to both a human-readable and a machine-processable description of the API service. The machine-processable description is written in the Web Application Description Language (WADL). -