Руководство Разработчика для Cisco Cisco Prime Performance Manager 1.3
Cisco Prime Performance Manager REST API Guide
Copyright 2012 Cisco Systems
- 17 -
Format:
Refer to section 14.8 RFC 2616 Authorization header.
Refer to section 14.8 RFC 2616 Authorization header.
Additional Notes:
• Verify that this header is sent with the request if Prime Performance Manager has user access enabled
• The userId and password defined in the Prime Performance Manager server must be base64 encoded and
added to the header as defined in the HTTP standards.
5.10 HTTP Response Headers
The following table shows the HTTP Response headers supported.
Table 21 – HTTP Response Headers
Header Name
Sample Value
Description
Allow
(HTTP/1.1)
For example, “GET”
This header is generated along with
status code “405” in response to
request with a method (HEAD,
POST, PUT, DELETE) that is not
supported for that resource.
status code “405” in response to
request with a method (HEAD,
POST, PUT, DELETE) that is not
supported for that resource.
Cache-Control
(HTTP/1.1)
For example, “no-cache” OR “max-age=3600”
When “no-cache” is found the client
should not cache the response.
Otherwise if max-age is found,
response may be cached by the
client. And the max-age value tells
the client how long in seconds the
response should be cached.
should not cache the response.
Otherwise if max-age is found,
response may be cached by the
client. And the max-age value tells
the client how long in seconds the
response should be cached.
Content-Type
For example. “application/xml;charset=UTF-8”
The content-type of the response
followed by the charset encoding.
followed by the charset encoding.
Date
For example. “Date Fri, 27 Jan 2012 20:29:02
GMT”
GMT”
The date the response was created.
WWW-Authenticate
“Basic realm=RESTSecureArea”
This header is sent back to the client
when Prime Performance Manager
has user access (authentication)
enabled, and the system failed to
authenticate the user’s request (see
the Authorization
Request header above). This
response header conforms to the
HTTP Basic WWW-Authenticate
header defined in HTTP 1.0
standards.
when Prime Performance Manager
has user access (authentication)
enabled, and the system failed to
authenticate the user’s request (see
the Authorization
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 there is more than one page
available for the requested report.
when there is more than one page
available for the requested report.