YADE Parameter Reference - HTTPFragment

This attribute identifies the current fragment. Any number of fragments can be used and are distinguished by YADE according their name.

A fragment is referenced by a transfer profile using the value of this attribute.

• Schema: URLConnection, URLConnection
• Mapping:
  • auth_method

A URL connection specifies parameters such as a Hostname, Port, Account by which a connection is established within the URL.

The use of URLs depends on the server system, e.g. the following protocols and configuration items could be used:
http|https :// [ account [ : password ] @ ] hostname [ : port ]
If the port is empty, the default ports will be used:

• HTTP: 80
• HTTPS: 443

• Schema: BasicAuthentication, BasicAuthentication

The BasicAuthentication element specifies the credentials for authentication with a server, e.g. using an FTP protocol or a Proxy Protocol. Child elements include:

• Account for authentication. For Windows Systems an account could include the domain.
• Password for authentication. Passwords are not displayed in the YADE log files.

BasicAuthentication is available for a number of File Transfer Protocols and Proxy Protocols. The drawback with BasicAuthentication is that passwords are stored directly in configuration files. In order to avoid this you could switch to using File Transfer Protocols that allow SSHAuthentication, e.g. SFTP.

• Schema: CredentialStoreFragmentRef, CredentialStoreFragmentRef

This element references the fragment that is used to insert configuration items from a secure store into a file transfer configuration.

Any number of reusable CredentialStoreFragment elements can be configured and are distinguished by YADE based on their name attribute.

The reference to a fragment is based on the value of the ref attribute of this element to the corresponding name attribute of the CredentialStoreFragment element.

Support for a jump host.

Note: Availability starting with YADE-488.

• Schema: JumpFragmentRef, JumpFragmentRef

Any number of reusable JumpFragment elements can be configured and are distinguished by YADE based on their name attribute.

This element identifies the JumpFragment that is applied for use of a jump host in a file transfer.

The reference to a fragment is based on the value of the ref attribute of this element to the corresponding name attribute of the JumpFragment element.

Proxies can make use of different protocols, a HTTPProxy - as the name suggests - will use the HTTP protocol

HTTP proxies optionally support authentication.

• Schema: HTTPProxy, HTTPProxy
• Mapping:
  • proxy_protocol
• Release:
  • YADE-351 Availability starting with 1.11.

Proxies can make use of different protocols, a HTTPProxy - as the name suggests - will use the HTTP protocol

HTTP proxies optionally support authentication.

• Schema: HTTPHeaders
• Mapping:
  • http_headers
• Release:
  • YADE-594 Availability starting with 1.13.16.

HTTP headers let the client and the server pass additional information with an HTTP request or response.
YADE allows to specify HTTP headers individually per HTTP(S) transfer fragment or HTTP(S) transfer fragment reference.

• Schema: HTTPHeader, HTTPHeader
• Release:
  • YADE-594 Availability starting with 1.13.16.

This parameter specifies a HTTP header, which is used for a HTTP(S) file transfer.
Name and value are separated by the first space, e.g.:

• Accept text/html
• Content-Type application/json; charset=utf-8
• Keep-Alive timeout=5, max=1000