Cisco Cisco Prime Performance Manager 1.5 Developer's Guide
Cisco Prime Performance Manager1.5 REST API Guide
the Authorization
Request header above). This
response header conforms to the
HTTP Basic WWW-Authenticate
header defined in HTTP 1.0
standards.
Request header above). This
response header conforms to the
HTTP Basic WWW-Authenticate
header defined in HTTP 1.0
standards.
Content-Range
pages [page number]/[total pages
For example. “pages 2/10”
In the example the current response contains page 2
of a report that has 10 pages total.
of a report that has 10 pages total.
This response header is sent back
when more than one page is
available for the requested report.
when more than one page is
available for the requested report.
5.11 HTTP Status Code
The following table shows the HTTP Status codes supported.
Table 36 – HTTP Status Codes
Status Code
Description
200
OK response. The request was correctly processed, and a response with a content body
was produced.
was produced.
204
No content found. That is, the request was a valid request; however, the system did not
have any content available for the resource requested. For example, this would be the
case for a valid report that has no data in it.
have any content available for the resource requested. For example, this would be the
case for a valid report that has no data in it.
Notice that no message-body (no content) is found in an HTTP response that has 204 as
the status code.
the status code.
206
Partial content. This status code is returned when a partial set of the report data has been
returned. It is sent along with a “Content-Range” header. This status code indicates that
pagination is required to retrieve the remaining data for the requested report.
returned. It is sent along with a “Content-Range” header. This status code indicates that
pagination is required to retrieve the remaining data for the requested report.
400
Bad Request. This happens when the request has an invalid parameter, or it is missing a
required parameter. Or it could also be the case when the requested resource path is not
in the expected syntax.
required parameter. Or it could also be the case when the requested resource path is not
in the expected syntax.
401
Authentication Failed. This status code is generated when the Prime Performance
Manager server is running with user access (authentication) enabled, and the REST API
server was unable to authenticate the user.
Manager server is running with user access (authentication) enabled, and the REST API
server was unable to authenticate the user.
403
Forbidden or Access Denied. This status code is generated when the requested report is
currently disabled in the Prime Performance Manager system. A report can be disabled
when its “poller” is disabled in Prime Performance Manager.
currently disabled in the Prime Performance Manager system. A report can be disabled
when its “poller” is disabled in Prime Performance Manager.
404
Resource Not Found. This status code is generated when the requested resource does not
exist in the Prime Performance Manager REST API server. For example, if the request is
for a report that is not found on the Prime Performance Manager server.
exist in the Prime Performance Manager REST API server. For example, if the request is
for a report that is not found on the Prime Performance Manager server.
405
Method Not Allowed. This status code is generated when the requested method (HEAD,
POST, PUT or DELETE) is not supported for that resource.
POST, PUT or DELETE) is not supported for that resource.
406
Not Acceptable. This status code is generated when the “Accept” header sent in the
request is not supported by the REST API.
request is not supported by the REST API.