Data Transformation Engine XML Adapter Reference Guide

ManualsBrandsHP ManualsServerHP NonStop G-Series

Chapter 5 – Using the Adapter URL Encoding

XML Data Adapter Reference Guide

The

url_path

of an FTP URL has the following syntax:

cwd1/cwd2/.../cwdN/name

;type=

typecode

where

cwd1

through

cwdN

and

name

are (possibly encoded) strings and

typecode

is one of the characters

a, i, or d. The

cwdx

and

name

parts may be empty. You

may omit

;type=

typecode

The whole

url_path

may be omitted, including the /, delimiting it from the prefix

containing

user

password

host

, and

port

. The

url_path

is interpreted as a

series of FTP commands as follows:

♦ Each

cwd

element is to be sequentially supplied as the argument to a CWD

(change working directory) command.

♦ If the typecode is

d, perform an NLST (name list) command with

name

as the

argument, and interpret the results as a file directory listing.

♦ Otherwise, perform a

TYPE command with

typecode

as the argument and

then access the file whose name is

name

(for example, using the RETR

command).

Note The

typecode

argument has been extended beyond what is supported by the

RFC, specifically the D1, D2, D3, and D4 sections. Also,

host

port

may be

excluded, though it is rarely useful to do so;

host

defaults to localhost.

URL Encoding

The URL does not need to be completely URL-encoded. You only need to use

escape characters for tokens specifically used in a URL, as shown in the following

table. Any URL that contains spaces must be enclosed in quotes; for example:

-URL “FTP://Home Machine/FTP Files”

Tokens Replaced with

% (percent) %25

@ (at) %40

/ (forward slash) %2F

: (colon) %3A

; (semicolon) %3B