|
The DCP request indicates the resource to which the request
method in the request line are to be applied.
The DCP request URI is a Uniform Resource Identifier that has been
extended to support devices modeled as objects.
Syntax
The two options for request URI are dependent on the nature of the
request.
The dcpUrl
form is only allowed when the request is being made to a
proxy (or intermediary). The proxy
is requested to forward the request and return the response.
The proxy may
forward the request on to another proxy or directly to the target specified by the
dcpUrl. In order to avoid request loops, a proxy must be able to recognize all of its
target names, including any aliases, local variations, and the numeric IP address.
Example: Request Line with absolute DCP URL
GET DCP://x10.domain.com/X10(AC=1,HC=A).Power DCP/1.0
The most common form of the DCP request URI is that used to identify a resource on a target. In this case, only the absDcpPath
of the URI is transmitted.
Example: Request Line with absolute DCP Path
GET X10(AC=1,HC=A).Power DCP/1.0
Note: The
absDcpPath cannot be empty; if
none is present in the original URI, it must be given as "/" (the
target root).
The DCP request URI is transmitted as an encoded string, where some characters may be
escaped using the ' "%" hex
hex ' encoding defined by RFC 1738. The
target must decode the DCP request URI to properly interpret the request.
|