<portal_uri>/mycontent[.<format>]
myMaps, myServices, myScenes, myDatas, myAccount, myGroups, keys
The root resource of my content. By executing a GET request on myContent, you can get the information of its child resource, including myMaps, myServices, myAccount, etc.
Supported Methods:
Supported output formats: rjson, json, html, xml.
Execute the HTTP request on the following URI, where supermapiserver is the server name, with rjson being the output format.
http://supermapiportal:8090/iportal/web/mycontent.rjson
Get the resource representation for myContent, that is, the access to resources myMaps, myServices, myAccount, etc.
Execute a GET request on the myContent resource, and get the information list of its child resources, including myMaps, myServices, myAccount, etc. The returned representation structure of a resource is:
| Field | Type | Description |
| name | String | Resource name. |
| path | String | Resource URI. |
| resourceConfigID | String | The signal of the current resource implementation class in the resource configuration file. |
| resourceType | ResourceType | The resource type. |
| supportedMediaTypes | String[] | The supported representation formats. |
The returned rjson format representation after executing the GET request on the user resource http://localhost:8090/iportal/web/mycontent.rjson is as follows:
[
{
"name": "maps",
"path": "http://localhost:8090/iportal/web/mycontent/maps",
"resourceConfigID": null,
"resourceType": null,
"supportedMediaTypes": null
},
{
"name": "services",
"path": "http://localhost:8090/iportal/web/mycontent/services",
"resourceConfigID": null,
"resourceType": null,
"supportedMediaTypes": null
},
{
"name": "datas",
"path": "http://localhost:8090/iportal/web/mycontent/datas",
"resourceConfigID": null,
"resourceType": null,
"supportedMediaTypes": null
},
{
"name": "account",
"path": "http://localhost:8090/iportal/web/mycontent/account",
"resourceConfigID": null,
"resourceType": null,
"supportedMediaTypes": null
},
{
"name": "groups",
"path": "http://localhost:8090/iportal/web/mycontent/groups",
"resourceConfigID": null,
"resourceType": null,
"supportedMediaTypes": null
},
{
"name": "message",
"path": "http://localhost:8090/iportal/web/mycontent/message",
"resourceConfigID": null,
"resourceType": null,
"supportedMediaTypes": null
},
{
"name": "scenes",
"path": "http://localhost:8090/iportal/web/mycontent/scenes",
"resourceConfigID": null,
"resourceType": null,
"supportedMediaTypes": null
},
{
"name": "keys",
"path": "http://localhost:8090/iportal/web/mycontent/keys",
"resourceConfigID": null,
"resourceType": null,
"supportedMediaTypes": null
}
]
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 myContent resource exists, or if the myContent resource can be accessed by clients. It can also determine if the myContent resource supports an output format <format> if performed on a URI with .<format> included.