DEST=

A destination identifies a URL to request for a task. You can identify a deck or digest URL with a full, partial, or relative path. You identify a card with its name.

Syntax

HDML 3.0 uses the same destination syntax as conventional URLs (as specified in RFC 1808 and RFC 1738). The 3.1 UP.Browser understands both HTTP and HTTPS addressing schemes (and the httpurl syntax specified in RFC 1738). If you do not specify a scheme, the UP.Browser assumes the HTTP addressing scheme.

The UP.Phone converts all relative URLs to absolute URLs before transmitting them to the UP.Link server. The following symbols have special meanings when you use them in a path:

Symbol	Meaning
`?`	The URL of the current deck with no arguments
`?arg1=value arg2=value`...	The URL of the current deck with the specified arguments

Destination examples

For a full description of URL syntax, see the RFC 1808 and RFC 1738. The following are some simple examples.

Destination	Meaning
`http://uplanet.com/adir/ deck.hdml`	An absolute path identifying the deck `deck.hdml`.
`http://uplanet.com/adir/ deck.hdml?arg1=2`	An absolute path identifying the deck `deck.hdml` with the CGI argument `ARG1` set to `2`.
`http://uplanet.com/adir/ deck.hdml#acard`	An absolute path identifying the card named `acard` in the `deck.hdml` deck.
`http://uplanet.com/adir/ deck.hdml?arg1=2#acard`	An absolute path identifying the card named `acard` in the `deck.hdml` deck with the CGI argument `ARG1` set to `2`.
`#acard`	A relative path identifying `acard`. This destination is meaningful only if you specify it in the deck containing `acard`.
`otherdeck.hdml`	A relative path identifying a deck in the same directory.
`subdir/yad.hdml`	A relative path identifying a deck in the `subdir` subdirectory of the same directory.
`../deck.hdml`	A relative path identifying a deck in a directory one level up from the directory containing the current deck. Additional `../` strings can be prepended to specify directories further up the directory tree.