userRequests


URI

<serverStatus uri>/users[.<format>]

Supported methods

GET, HEAD

Parent resource

serverStatus

Child resources

userRequestsStatistics

Introduction

userRequests is the user query resource. You can view all users corresponding to service access records in a certain time.

Supported Methods:

Supported output formats: rjson, json, html, xml.

Resource hierarchy

 

HTTP request methods

Implement the HTTP request on the following URI, where supermapiserver is the server name, with rjson being the output format.

http://supermapiserver:8090/iserver/manager/serverstatus/users.rjson

GET request

Gets all users corresponding to service access records in a certain time.

Request parameter

Implement the GET request on the userRequests . The URL can contain the following parameters:

Name Type Description
startTime long The start time of service access record. If it is not positive number, it will be queried from the earliest record. The value is the milliseconds from 00:00:00 GMT January 1, 1970.
endTime long The end time of service access record. If it is not positive number, the server time will be the end time. The value is the milliseconds from 00:00:00 GMT January 1, 1970.

Response example

Perform GET request on userRequests resource http://localhost:8090/iserver/manager/serverstatus/users.rjson?startTime=1408982476609&endTime=1409104315939. You can get the service access records in a certain time, and the rjson responding result is as follows:

[

    "admin",

    "anonymous"

]

HEAD request

Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. The meta-information includes the media-type, content-encoding, transfer-encoding, content-length, etc.

HEAD request can be used to check if the userRequests resource exists, or if the userRequests resource can be accessed by clients. It can also determine if the userRequests resource supports an output format <format> if performed on a URI with .<format> included.

See