Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EncryptContent/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EncryptContent/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EncryptContent/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EncryptContent/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EncryptContent</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Encrypts or 
Decrypts a FlowFile using either symmetric encryption with a password and 
randomly generated salt, or asymmetric encryption using a public and secret 
key.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>encryption, decryption, password, JCE, 
OpenPGP, PGP, GPG</p><h3>Properties: </h3><p>In the list below, the names of 
required properties appear in <strong>bold</strong>. Any other properties (not 
in bold) are considered optional. The table also indicates any default values, 
and whether a property is considered "sensitive", meaning that its value will 
be encrypted. Before entering a value in a sensitive property, ensure that the 
<strong>nifi.properties</strong> file has an entry for the property 
<strong>nifi.sensitive.props.
 key</strong>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Mode</strong></td><td id="default-value">Encrypt</td><td 
id="allowable-values"><ul><li>Encrypt</li><li>Decrypt</li></ul></td><td 
id="description">Specifies whether the content should be encrypted or 
decrypted</td></tr><tr><td id="name"><strong>Key Derivation 
Function</strong></td><td id="default-value">NIFI_LEGACY</td><td 
id="allowable-values"><ul><li>NIFI_LEGACY</li><li>OPENSSL_EVP_BYTES_TO_KEY</li></ul></td><td
 id="description">Specifies the key derivation function to generate the key 
from the password (and salt)</td></tr><tr><td id="name"><strong>Encryption 
Algorithm</strong></td><td id="default-value">MD5_128AES</td><td 
id="allowable-values"><ul><li>MD5_128AES</li><li>MD5_192AES</li><li>MD5_256AES</li><li>MD5_DES</li><li>MD5_RC2</li><li>SHA1_RC2</li><li>SHA1_DES</li><li>SHA_128AES</li><li>SHA_192AES</li><li>SHA_256AES</li><li>
 
SHA_40RC2</li><li>SHA_128RC2</li><li>SHA_40RC4</li><li>SHA_128RC4</li><li>SHA256_128AES</li><li>SHA256_192AES</li><li>SHA256_256AES</li><li>SHA_2KEYTRIPLEDES</li><li>SHA_3KEYTRIPLEDES</li><li>SHA_TWOFISH</li><li>PGP</li><li>PGP_ASCII_ARMOR</li></ul></td><td
 id="description">The Encryption Algorithm to use</td></tr><tr><td 
id="name">Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Password to use for 
encrypting or decrypting the data<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Public Keyring File</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">In 
a PGP encrypt mode, this keyring contains the public key of the 
recipient</td></tr><tr><td id="name">Public Key User Id</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">In 
a PGP encrypt mode, this user id of the recipient</td></tr><tr><td 
id="name">Private Keyring File</td><td id="default-value">
 </td><td id="allowable-values"></td><td id="description">In a PGP decrypt 
mode, this keyring contains the private key of the recipient</td></tr><tr><td 
id="name">Private Keyring Passphrase</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">In a PGP decrypt mode, this is 
the private keyring passphrase<br/><strong>Sensitive Property: 
true</strong></td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Any
 FlowFile that is successfully encrypted or decrypted will be routed to 
success</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be encrypted 
or decrypted will be routed to failure</td></tr></table><h3>Reads Attributes: 
</h3>None specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EncryptContent</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Encrypts or 
Decrypts a FlowFile using either symmetric encryption with a password and 
randomly generated salt, or asymmetric encryption using a public and secret 
key.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>encryption, decryption, password, JCE, 
OpenPGP, PGP, GPG</p><h3>Properties: </h3><p>In the list below, the names of 
required properties appear in <strong>bold</strong>. Any other properties (not 
in bold) are considered optional. The table also indicates any default values, 
and whether a property is considered "sensitive", meaning that its value will 
be encrypted. Before entering a value in a sensitive property, ensure that the 
<strong>nifi.properties</strong> file has an entry for the property 
<strong>nifi.sensitive.props.
 key</strong>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Mode</strong></td><td id="default-value">Encrypt</td><td 
id="allowable-values"><ul><li>Encrypt</li><li>Decrypt</li></ul></td><td 
id="description">Specifies whether the content should be encrypted or 
decrypted</td></tr><tr><td id="name"><strong>Key Derivation 
Function</strong></td><td id="default-value">BCRYPT</td><td 
id="allowable-values"><ul><li>NiFi Legacy KDF <img 
src="../../html/images/iconInfo.png" alt="MD5 @ 1000 iterations" title="MD5 @ 
1000 iterations"></img></li><li>OpenSSL EVP_BytesToKey <img 
src="../../html/images/iconInfo.png" alt="Single iteration MD5 compatible with 
PKCS#5 v1.5" title="Single iteration MD5 compatible with PKCS#5 
v1.5"></img></li><li>Bcrypt <img src="../../html/images/iconInfo.png" 
alt="Bcrypt with configurable work factor. See Admin Guide" title="Bcrypt with 
configurable work factor. See Admin Guide"
 ></img></li><li>Scrypt <img src="../../html/images/iconInfo.png" alt="Scrypt 
 >with configurable cost parameters. See Admin Guide" title="Scrypt with 
 >configurable cost parameters. See Admin Guide"></img></li><li>PBKDF2 <img 
 >src="../../html/images/iconInfo.png" alt="PBKDF2 with configurable hash 
 >function and iteration count. See Admin Guide" title="PBKDF2 with 
 >configurable hash function and iteration count. See Admin 
 >Guide"></img></li><li>None <img src="../../html/images/iconInfo.png" alt="The 
 >cipher is given a raw key conforming to the algorithm specifications" 
 >title="The cipher is given a raw key conforming to the algorithm 
 >specifications"></img></li></ul></td><td id="description">Specifies the key 
 >derivation function to generate the key from the password (and 
 >salt)</td></tr><tr><td id="name"><strong>Encryption 
 >Algorithm</strong></td><td id="default-value">MD5_128AES</td><td 
 >id="allowable-values"><ul><li>MD5_128AES <img 
 >src="../../html/images/iconInfo.png" alt="org.apache.nifi.securi
 ty.util.EncryptionMethod@3c291aad[Algorithm 
name=PBEWITHMD5AND128BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" 
title="org.apache.nifi.security.util.EncryptionMethod@3c291aad[Algorithm 
name=PBEWITHMD5AND128BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_192AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND192BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND192BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_256AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
 name=PBEWITHMD5AND256BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND256BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_DES <img src="../../html/images/iconInfo.png" 
alt="EncryptionMethod[Algorithm name=PBEWITHMD5ANDDES,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5ANDDES,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_RC2 <img src="../../html/images/iconInfo.png" 
alt="EncryptionMethod[Algorithm name=PBEWITHMD5ANDRC2,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Ke
 yed cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5ANDRC2,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA1_RC2 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA1ANDRC2,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHSHA1ANDRC2,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>SHA1_DES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA1ANDDES,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHSHA1ANDDES,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible 
 with strong KDFs=false,Keyed cipher=false]"></img></li><li>SHA_128AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_192AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_256AES <img src="../../html/images/iconI
 nfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_40RC2 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_128RC2 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC2-CBC,Requires unlimited strength JCE policy=
 false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_40RC4 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_128RC4 <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm name=PBEWIT
 HSHAAND128BITRC4,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_128AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_192AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,C
 ompatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_256AES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_2KEYTRIPLEDES <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND2-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND2-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_3KEYTRIPLE
 DES <img src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND3-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND3-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_TWOFISH <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAANDTWOFISH-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAANDTWOFISH-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>PGP <img src="../../html/images/iconInfo.png" 
alt="EncryptionMethod[Algorithm name=PGP,Requires unlimited strengt
 h JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]" title="EncryptionMethod[Algorithm 
name=PGP,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>PGP_ASCII_ARMOR <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PGP-ASCII-ARMOR,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PGP-ASCII-ARMOR,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>AES_CBC <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/CBC/PKCS7Padding,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=true,Keyed 
cipher=true]" title="EncryptionMethod[Algorithm 
name=AES/CBC/PKCS7Padding,Requires
  unlimited strength JCE policy=false,Algorithm Provider=BC,Compatible with 
strong KDFs=true,Keyed cipher=true]"></img></li><li>AES_CTR <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/CTR/NoPadding,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=true,Keyed cipher=true]" 
title="EncryptionMethod[Algorithm name=AES/CTR/NoPadding,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=true,Keyed cipher=true]"></img></li><li>AES_GCM <img 
src="../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/GCM/NoPadding,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=true,Keyed cipher=true]" 
title="EncryptionMethod[Algorithm name=AES/GCM/NoPadding,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=true,Keyed cipher=true]"></img></li></ul></td><td id="description">The 
Encry
 ption Algorithm to use</td></tr><tr><td id="name"><strong>Allow insecure 
cryptographic modes</strong></td><td id="default-value">not-allowed</td><td 
id="allowable-values"><ul><li>Allowed <img src="../../html/images/iconInfo.png" 
alt="Operation will not be blocked and no alerts will be presented when unsafe 
combinations of encryption algorithms and passwords are provided" 
title="Operation will not be blocked and no alerts will be presented when 
unsafe combinations of encryption algorithms and passwords are 
provided"></img></li><li>Not Allowed <img src="../../html/images/iconInfo.png" 
alt="When set, operation will be blocked and alerts will be presented to the 
user if unsafe combinations of encryption algorithms and passwords are provided 
on a JVM with limited strength crypto. To fix this, see the Admin Guide." 
title="When set, operation will be blocked and alerts will be presented to the 
user if unsafe combinations of encryption algorithms and passwords are provided 
on a JVM with lim
 ited strength crypto. To fix this, see the Admin 
Guide."></img></li></ul></td><td id="description">Overrides the default 
behavior to prevent unsafe combinations of encryption algorithms and short 
passwords on JVMs with limited strength cryptographic jurisdiction 
policies</td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Password to use for encrypting or decrypting the data<br/><strong>Sensitive 
Property: true</strong></td></tr><tr><td id="name">Raw Key 
(hexadecimal)</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">In keyed encryption, this is 
the raw key, encoded in hexadecimal<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Public Keyring File</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">In 
a PGP encrypt mode, this keyring contains the public key of the 
recipient</td></tr><tr><td id="name">Public Key User Id</td
 ><td id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">In a PGP encrypt mode, this user id of the 
 >recipient</td></tr><tr><td id="name">Private Keyring File</td><td 
 >id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">In a PGP decrypt mode, this keyring contains the private key 
 >of the recipient</td></tr><tr><td id="name">Private Keyring 
 >Passphrase</td><td id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">In a PGP decrypt mode, this is the private keyring 
 >passphrase<br/><strong>Sensitive Property: 
 >true</strong></td></tr></table><h3>Relationships: </h3><table 
 >id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Any
 > FlowFile that is successfully encrypted or decrypted will be routed to 
 >success</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be 
 >encrypted or decrypted will be routed to failure</td></tr></table><h3>Reads 
 >Attributes: </h3>None specified.<h3>Writes Attributes:
  </h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchDistributedMapCache/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchDistributedMapCache/index.html?rev=1730777&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchDistributedMapCache/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchDistributedMapCache/index.html
 Wed Feb 17 02:20:53 2016
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>FetchDistributedMapCache</title><link 
rel="stylesheet" href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Computes a cache 
key from FlowFile attributes, for each incoming FlowFile, and fetches the value 
from the Distributed Map Cache associated with that key. The incoming 
FlowFile's content is replaced with the binary data received by the Distributed 
Map Cache. If there is no value stored under that key then the flow file will 
be routed to 'not-found'. Note that the processor will always attempt to read 
the entire cached value into memory before placing it in it's destination. This 
could be potentially problematic if the cached value is very 
large.</p><h3>Tags: </h3><p>map, cache, fetch, distributed</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered option
 al. The table also indicates any default values, and whether a property 
supports the <a href="../../html/expression-language-guide.html">NiFi 
Expression Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Cache Entry Identifier</strong></td><td 
id="default-value">${hash.value}</td><td id="allowable-values"></td><td 
id="description">A FlowFile attribute, or the results of an Attribute 
Expression Language statement, which will be evaluated against a FlowFile in 
order to determine the value used to identify duplicates; it is this value that 
is cached<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Distributed Cache 
Service</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>DistributedMapCacheClient<br/><strong>Implementation:</strong><br/><a
 href="../org.apache.nifi.distributed.cac
 
he.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a></td><td
 id="description">The Controller Service that is used to get the cached 
values.</td></tr><tr><td id="name">Put Cache Value In Attribute</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
set, the cache value received will be put into an attribute of the FlowFile 
instead of a the content of theFlowFile. The attribute key to put to is 
determined by evaluating value of this property.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Max Length To Put 
In Attribute</td><td id="default-value">256</td><td 
id="allowable-values"></td><td id="description">If routing the cache value to 
an attribute of the FlowFile (by setting the "Put Cache Value in attribute" 
property), the number of characters put to the attribute value will be at most 
this amount. This is important because attributes are held in memory and large 
attributes wi
 ll quickly cause out of memory issues. If the output goes longer than this 
value, it will be truncated to fit. Consider making this smaller if 
able.</td></tr><tr><td id="name">Character Set</td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">The Character Set in which the cached value is encoded. This 
will only be used when routing to an 
attribute.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>If
 the cache was successfully communicated with it will be routed to this 
relationship</td></tr><tr><td>failure</td><td>If unable to communicate with the 
cache or if the cache entry is evaluated to be blank, the FlowFile will be 
penalized and routed to this relationship</td></tr><tr><td>not-found</td><td>If 
a FlowFile's Cache Entry Identifier was not found in the cache, it will be 
routed to this relationship</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>W
 rites Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>user-defined</td><td>If
 the 'Put Cache Value In Attribute' property is set then whatever it is set to 
will become the attribute key and the value would be whatever the response was 
from the Distributed Map Cache.</td></tr></table><h3>See Also:</h3><p><a 
href="../org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a>,
 <a 
href="../org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html">DistributedMapCacheServer</a>,
 <a 
href="../org.apache.nifi.processors.standard.PutDistributedMapCache/index.html">PutDistributedMapCache</a></p></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchSFTP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchSFTP/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchSFTP/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchSFTP/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>FetchSFTP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Fetches the 
content of a file from a remote SFTP server and overwrites the contents of an 
incoming FlowFile with the content of the remote file.</p><h3>Tags: 
</h3><p>sftp, get, retrieve, files, fetch, remote, ingest, source, 
input</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, whether a 
property supports the <a href="../../html/expression-language-guide.html">NiFi 
Expression Language</a>, and whether a property is considered "sensitive", 
meaning that its value will be encrypted. Before entering a value in a 
sensitive property, ensure that the <strong>nifi.properties</strong> file has 
an entry for the property
  <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Hostname</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully-qualified hostname or 
IP address of the host to fetch the data from<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td 
id="name"><strong>Port</strong></td><td id="default-value">22</td><td 
id="allowable-values"></td><td id="description">The port to connect to on the 
remote host to fetch the data from<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Username</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description
 ">Password for the user account<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Private Key Path</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully qualified path to the Private Key file</td></tr><tr><td id="name">Private 
Key Passphrase</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Password for the private 
key<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
id="name"><strong>Remote File</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully qualified filename on 
the remote system<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Completion 
Strategy</strong></td><td id="default-value">None</td><td 
id="allowable-values"><ul><li>None <img src="../../html/images/iconInfo.png" 
alt="Leave the file as-is" title="Leave the file as-is"></img></li><li>Move 
File <img src="../../html/imag
 es/iconInfo.png" alt="Move the file to the directory specified by the &lt;Move 
Destination Directory&gt; property" title="Move the file to the directory 
specified by the &lt;Move Destination Directory&gt; 
property"></img></li><li>Delete File <img src="../../html/images/iconInfo.png" 
alt="Deletes the original file from the remote system" title="Deletes the 
original file from the remote system"></img></li></ul></td><td 
id="description">Specifies what to do with the original file on the server once 
it has been pulled into NiFi. If the Completion Strategy fails, a warning will 
be logged but the data will still be transferred.</td></tr><tr><td 
id="name">Move Destination Directory</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The directory on the remote 
server to the move the original file to once it has been ingested into NiFi. 
This property is ignored unless the Completion Strategy is set to "Move File". 
The specified directory must already exist on
 the remote system, or the rename will fail.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>Connection 
Timeout</strong></td><td id="default-value">30 sec</td><td 
id="allowable-values"></td><td id="description">Amount of time to wait before 
timing out while creating a connection</td></tr><tr><td id="name"><strong>Data 
Timeout</strong></td><td id="default-value">30 sec</td><td 
id="allowable-values"></td><td id="description">When transferring a file 
between the local and remote system, this value specifies how long is allowed 
to elapse without any data being transferred between systems</td></tr><tr><td 
id="name"><strong>Send Keep Alive On Timeout</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not to send a single Keep Alive message 
when SSH socket times out</td></tr><tr><td id="name">Host Key File</td><td 
id="default-value"></td><td id="a
 llowable-values"></td><td id="description">If supplied, the given file will be 
used as the Host Key; otherwise, no use host key file will be 
used</td></tr><tr><td id="name"><strong>Strict Host Key 
Checking</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not strict enforcement of hosts keys 
should be applied</td></tr><tr><td id="name"><strong>Use 
Compression</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not ZLIB compression should be used when 
transferring files</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles that are received are routed to 
success</td></tr><tr><td>comms.failure</td><td>Any FlowFile that could not be 
fetched from the remote server due to a communications fai
 lure will be transferred to this 
Relationship.</td></tr><tr><td>not.found</td><td>Any FlowFile for which we 
receive a 'Not Found' message from the remote server will be transferred to 
this Relationship.</td></tr><tr><td>permission.denied</td><td>Any FlowFile that 
could not be fetched from the remote server due to insufficient permissions 
will be transferred to this Relationship.</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>sftp.remote.host</td><td>The
 hostname or IP address from which the file was 
pulled</td></tr><tr><td>sftp.remote.port</td><td>The port that was used to 
communicate with the remote SFTP 
server</td></tr><tr><td>sftp.remote.filename</td><td>The name of the remote 
file that was pulled</td></tr><tr><td>filename</td><td>The filename is updated 
to point to the filename fo the remote file</td></tr></table><h3>See 
Also:</h3><p><a href="../org.apache.nifi
 .processors.standard.GetSFTP/index.html">GetSFTP</a>, <a 
href="../org.apache.nifi.processors.standard.PutSFTP/index.html">PutSFTP</a>, 
<a href="../org.apache.nifi.processors.standard.GetFTP/index.html">GetFTP</a>, 
<a 
href="../org.apache.nifi.processors.standard.PutFTP/index.html">PutFTP</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>FetchSFTP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Fetches the 
content of a file from a remote SFTP server and overwrites the contents of an 
incoming FlowFile with the content of the remote file.</p><h3>Tags: 
</h3><p>sftp, get, retrieve, files, fetch, remote, ingest, source, 
input</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, whether a 
property supports the <a href="../../html/expression-language-guide.html">NiFi 
Expression Language</a>, and whether a property is considered "sensitive", 
meaning that its value will be encrypted. Before entering a value in a 
sensitive property, ensure that the <strong>nifi.properties</strong> file has 
an entry for the property
  <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Hostname</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully-qualified hostname or 
IP address of the host to fetch the data from<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td 
id="name"><strong>Port</strong></td><td id="default-value">22</td><td 
id="allowable-values"></td><td id="description">The port to connect to on the 
remote host to fetch the data from<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Username</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description
 ">Password for the user account<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Private Key Path</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully qualified path to the Private Key file</td></tr><tr><td id="name">Private 
Key Passphrase</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Password for the private 
key<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
id="name"><strong>Remote File</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully qualified filename on 
the remote system<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Completion 
Strategy</strong></td><td id="default-value">None</td><td 
id="allowable-values"><ul><li>None <img src="../../html/images/iconInfo.png" 
alt="Leave the file as-is" title="Leave the file as-is"></img></li><li>Move 
File <img src="../../html/imag
 es/iconInfo.png" alt="Move the file to the directory specified by the &lt;Move 
Destination Directory&gt; property" title="Move the file to the directory 
specified by the &lt;Move Destination Directory&gt; 
property"></img></li><li>Delete File <img src="../../html/images/iconInfo.png" 
alt="Deletes the original file from the remote system" title="Deletes the 
original file from the remote system"></img></li></ul></td><td 
id="description">Specifies what to do with the original file on the server once 
it has been pulled into NiFi. If the Completion Strategy fails, a warning will 
be logged but the data will still be transferred.</td></tr><tr><td 
id="name">Move Destination Directory</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The directory on the remote 
server to the move the original file to once it has been ingested into NiFi. 
This property is ignored unless the Completion Strategy is set to "Move File". 
The specified directory must already exist on
 the remote system, or the rename will fail.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>Connection 
Timeout</strong></td><td id="default-value">30 sec</td><td 
id="allowable-values"></td><td id="description">Amount of time to wait before 
timing out while creating a connection</td></tr><tr><td id="name"><strong>Data 
Timeout</strong></td><td id="default-value">30 sec</td><td 
id="allowable-values"></td><td id="description">When transferring a file 
between the local and remote system, this value specifies how long is allowed 
to elapse without any data being transferred between systems</td></tr><tr><td 
id="name"><strong>Send Keep Alive On Timeout</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not to send a single Keep Alive message 
when SSH socket times out</td></tr><tr><td id="name">Host Key File</td><td 
id="default-value"></td><td id="a
 llowable-values"></td><td id="description">If supplied, the given file will be 
used as the Host Key; otherwise, no use host key file will be 
used</td></tr><tr><td id="name"><strong>Strict Host Key 
Checking</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not strict enforcement of hosts keys 
should be applied</td></tr><tr><td id="name"><strong>Use 
Compression</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not ZLIB compression should be used when 
transferring files</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles that are received are routed to 
success</td></tr><tr><td>comms.failure</td><td>Any FlowFile that could not be 
fetched from the remote server due to a communications fai
 lure will be transferred to this 
Relationship.</td></tr><tr><td>not.found</td><td>Any FlowFile for which we 
receive a 'Not Found' message from the remote server will be transferred to 
this Relationship.</td></tr><tr><td>permission.denied</td><td>Any FlowFile that 
could not be fetched from the remote server due to insufficient permissions 
will be transferred to this Relationship.</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>sftp.remote.host</td><td>The
 hostname or IP address from which the file was 
pulled</td></tr><tr><td>sftp.remote.port</td><td>The port that was used to 
communicate with the remote SFTP 
server</td></tr><tr><td>sftp.remote.filename</td><td>The name of the remote 
file that was pulled</td></tr><tr><td>filename</td><td>The filename is updated 
to point to the filename fo the remote file</td></tr><tr><td>path</td><td>If 
the Remote File contains a direc
 tory name, that directory name will be added to the FlowFile using the 'path' 
attribute</td></tr></table><h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.GetSFTP/index.html">GetSFTP</a>, 
<a 
href="../org.apache.nifi.processors.standard.PutSFTP/index.html">PutSFTP</a>, 
<a href="../org.apache.nifi.processors.standard.GetFTP/index.html">GetFTP</a>, 
<a 
href="../org.apache.nifi.processors.standard.PutFTP/index.html">PutFTP</a></p></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.GetHTTP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.GetHTTP/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.GetHTTP/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.GetHTTP/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetHTTP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Fetches a file via 
HTTP</p><h3>Tags: </h3><p>get, fetch, poll, http, https, ingest, source, 
input</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, whether a 
property supports the <a href="../../html/expression-language-guide.html">NiFi 
Expression Language</a>, and whether a property is considered "sensitive", 
meaning that its value will be encrypted. Before entering a value in a 
sensitive property, ensure that the <strong>nifi.properties</strong> file has 
an entry for the property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><
 th>Description</th></tr><tr><td id="name"><strong>URL</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
URL to pull from<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Filename</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
filename to assign to the file when pulled<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context</td></tr><tr><td id="name">Username</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Username requi
 red to access the URL</td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password required to access the URL<br/><strong>Sensitive 
Property: true</strong></td></tr><tr><td id="name"><strong>Connection 
Timeout</strong></td><td id="default-value">30 sec</td><td 
id="allowable-values"></td><td id="description">How long to wait when 
attempting to connect to the remote server before giving up</td></tr><tr><td 
id="name"><strong>Data Timeout</strong></td><td id="default-value">30 
sec</td><td id="allowable-values"></td><td id="description">How long to wait 
between receiving segments of data from the remote server before giving up and 
discarding the partial file</td></tr><tr><td id="name">User Agent</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">What to report as the User Agent when we connect to the remote 
server</td></tr><tr><td id="name">Accept Content-Type</td><td 
id="default-value"><
 /td><td id="allowable-values"></td><td id="description">If specified, requests 
will only accept the provided Content-Type</td></tr><tr><td id="name">Follow 
Redirects</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If we receive a 3xx HTTP Status Code from the server, 
indicates whether or not we should follow the redirect that the server 
specifies</td></tr><tr><td id="name">Proxy Host</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully qualified hostname or IP address of the proxy server</td></tr><tr><td 
id="name">Proxy Port</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The port of the proxy 
server</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 files are transferred to the success relationship</td></tr></table><h3>Reads 
Attributes: </h3>None
  specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>filename</td><td>The
 filename is set to the name of the file on the remote 
server</td></tr><tr><td>mime.type</td><td>The MIME Type of the FlowFile, as 
reported by the HTTP Content-Type header</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetHTTP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Fetches data from 
an HTTP or HTTPS URL and writes the data to the content of a FlowFile. Once the 
content has been fetched, the ETag and Last Modified dates are remembered (if 
the web server supports these concepts). This allows the Processor to fetch new 
data only if the remote data has changed or until the state is cleared. That 
is, once the content has been fetched from the given URL, it will not be 
fetched again until the content on the remote server changes. Note that due to 
limitations on state management, stored "last modified" and etag fields never 
expire. If the URL in GetHttp uses Expression Language that is unbounded, there 
is the potential for Out of Memory Errors to occur.</p><h3>Tags: </h3><p>get, 
fetch, poll, http, https, ingest, source, input</p><h3>Properties: 
 </h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values, whether a property 
supports the <a href="../../html/expression-language-guide.html">NiFi 
Expression Language</a>, and whether a property is considered "sensitive", 
meaning that its value will be encrypted. Before entering a value in a 
sensitive property, ensure that the <strong>nifi.properties</strong> file has 
an entry for the property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td 
id="name"><strong>URL</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The URL to pull 
from<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Filename</strong></td><td id="default-value"></td><td 
id="allowable
 -values"></td><td id="description">The filename to assign to the file when 
pulled<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">SSL Context Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context</td></tr><tr><td id="name">Username</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Username required to access the 
URL</td></tr><tr><td id="name">Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Password required to access the 
URL<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
id="name"><strong>Connection Timeout</strong></td><td id="default-value">30 
sec</td><
 td id="allowable-values"></td><td id="description">How long to wait when 
attempting to connect to the remote server before giving up</td></tr><tr><td 
id="name"><strong>Data Timeout</strong></td><td id="default-value">30 
sec</td><td id="allowable-values"></td><td id="description">How long to wait 
between receiving segments of data from the remote server before giving up and 
discarding the partial file</td></tr><tr><td id="name">User Agent</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">What to report as the User Agent when we connect to the remote 
server</td></tr><tr><td id="name">Accept Content-Type</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
specified, requests will only accept the provided Content-Type</td></tr><tr><td 
id="name">Follow Redirects</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If we receive a 3xx HTTP Status Cod
 e from the server, indicates whether or not we should follow the redirect that 
the server specifies</td></tr><tr><td id="name">Proxy Host</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully qualified hostname or IP address of the proxy server</td></tr><tr><td 
id="name">Proxy Port</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The port of the proxy 
server</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 files are transferred to the success relationship</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>filename</td><td>The
 filename is set to the name of the file on the remote 
server</td></tr><tr><td>mime.type</td><td>The MIME Type of the FlowFile, as 
reported by the HTTP Content-Type header</td></tr></tabl
 e></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.HashContent/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.HashContent/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.HashContent/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.HashContent/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HashContent</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Calculates a hash 
value for the Content of a FlowFile and puts that hash value on the FlowFile as 
an attribute whose name is determined by the &lt;Hash Attribute Name&gt; 
property</p><h3>Tags: </h3><p>hash, content, MD5, SHA-1, 
SHA-256</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>Hash Attribute 
Name</strong></td><td id="default-value">hash.value</td><td 
id="allowable-values"></td><td id="description">The name of the FlowFile 
Attribute into which the Hash Value should
  be written. If the value already exists, it will be 
overwritten</td></tr><tr><td id="name"><strong>Hash Algorithm</strong></td><td 
id="default-value">MD5</td><td 
id="allowable-values"><ul><li>RIPEMD320</li><li>SHA-1</li><li>SHA-384</li><li>RIPEMD160</li><li>SHA</li><li>WHIRLPOOL</li><li>GOST3411</li><li>SHA-224</li><li>SHA-256</li><li>MD2</li><li>RIPEMD128</li><li>MD4</li><li>SHA-512</li><li>RIPEMD256</li><li>TIGER</li><li>MD5</li></ul></td><td
 id="description">Determines what hashing algorithm should be used to perform 
the hashing function</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 that are process successfully will be sent to this 
relationship</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be 
processed successfully will be sent to this relationship without any attribute 
being added</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><ta
 ble 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>&lt;Hash
 Attribute Name&gt;</td><td>This Processor adds an attribute whose value is the 
result of Hashing the existing FlowFile attributes. The name of this attribute 
is specified by the &lt;Hash Attribute Name&gt; 
property</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HashContent</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Calculates a hash 
value for the Content of a FlowFile and puts that hash value on the FlowFile as 
an attribute whose name is determined by the &lt;Hash Attribute Name&gt; 
property</p><h3>Tags: </h3><p>hash, content, MD5, SHA-1, 
SHA-256</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>Hash Attribute 
Name</strong></td><td id="default-value">hash.value</td><td 
id="allowable-values"></td><td id="description">The name of the FlowFile 
Attribute into which the Hash Value should
  be written. If the value already exists, it will be 
overwritten</td></tr><tr><td id="name"><strong>Hash Algorithm</strong></td><td 
id="default-value">MD5</td><td 
id="allowable-values"><ul><li>SHA-1</li><li>SHA-384</li><li>SKEIN-512-256</li><li>SKEIN-1024-384</li><li>BLAKE2B-160</li><li>SHA</li><li>KECCAK-288</li><li>WHIRLPOOL</li><li>SKEIN-512-384</li><li>SHA-224</li><li>SM3</li><li>BLAKE2B-512</li><li>SKEIN-512-128</li><li>KECCAK-256</li><li>BLAKE2B-384</li><li>OID.2.16.840.1.101.3.4.2.10</li><li>SKEIN-256-160</li><li>SHA-256</li><li>SHA3-256</li><li>KECCAK-384</li><li>SKEIN-256-128</li><li>KECCAK-224</li><li>SKEIN-512-512</li><li>SKEIN-1024-512</li><li>SKEIN-512-160</li><li>GOST3411</li><li>BLAKE2B-256</li><li>SKEIN-1024-1024</li><li>SHA3-384</li><li>OID.2.16.840.1.101.3.4.2.9</li><li>SHA-512/224</li><li>OID.2.16.840.1.101.3.4.2.8</li><li>OID.2.16.840.1.101.3.4.2.7</li><li>TIGER</li><li>RIPEMD256</li><li>SKEIN-256-256</li><li>SHA3-224</li><li>SHA3-512</li><li>RIPEMD320</li><li>2.
 
16.840.1.101.3.4.2.9</li><li>RIPEMD160</li><li>KECCAK-512</li><li>SKEIN-512-224</li><li>2.16.840.1.101.3.4.2.8</li><li>2.16.840.1.101.3.4.2.7</li><li>2.16.840.1.101.3.4.2.10</li><li>SHA-512/256</li><li>MD2</li><li>RIPEMD128</li><li>MD4</li><li>SHA-512</li><li>SKEIN-256-224</li><li>MD5</li></ul></td><td
 id="description">Determines what hashing algorithm should be used to perform 
the hashing function</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 that are process successfully will be sent to this 
relationship</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be 
processed successfully will be sent to this relationship without any attribute 
being added</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>&lt;Hash
 Attribute Name&gt;</td><td>This Processor adds an attribute 
 whose value is the result of Hashing the existing FlowFile attributes. The 
name of this attribute is specified by the &lt;Hash Attribute Name&gt; 
property</td></tr></table></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.InvokeHTTP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.InvokeHTTP/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.InvokeHTTP/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.InvokeHTTP/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>InvokeHTTP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>An HTTP client 
processor which converts FlowFile attributes to HTTP headers, with configurable 
HTTP method, url, etc.</p><h3>Tags: </h3><p>http, https, rest, 
client</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, whether a 
property supports the <a href="../../html/expression-language-guide.html">NiFi 
Expression Language</a>, and whether a property is considered "sensitive", 
meaning that its value will be encrypted. Before entering a value in a 
sensitive property, ensure that the <strong>nifi.properties</strong> file has 
an entry for the property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="propert
 ies"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>HTTP 
Method</strong></td><td id="default-value">GET</td><td 
id="allowable-values"></td><td id="description">HTTP request method (GET, POST, 
PUT, DELETE, HEAD, OPTIONS). Arbitrary methods are also supported but will be 
sent without a message body.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Remote URL</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Remote URL which will be connected to, including scheme, host, 
port, path.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextServic
 e</a></td><td id="description">The SSL Context Service used to provide client 
certificate information for TLS/SSL (https) connections.</td></tr><tr><td 
id="name"><strong>Connection Timeout</strong></td><td id="default-value">5 
secs</td><td id="allowable-values"></td><td id="description">Max wait time for 
connection to remote service.</td></tr><tr><td id="name"><strong>Read 
Timeout</strong></td><td id="default-value">15 secs</td><td 
id="allowable-values"></td><td id="description">Max wait time for response from 
remote service.</td></tr><tr><td id="name"><strong>Include Date 
Header</strong></td><td id="default-value">True</td><td 
id="allowable-values"><ul><li>True</li><li>False</li></ul></td><td 
id="description">Include an RFC-2616 Date header in the 
request.</td></tr><tr><td id="name"><strong>Follow Redirects</strong></td><td 
id="default-value">True</td><td 
id="allowable-values"><ul><li>True</li><li>False</li></ul></td><td 
id="description">Follow HTTP redirects issued by remote serve
 r.</td></tr><tr><td id="name">Attributes to Send</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Regular expression that defines which attributes to send as 
HTTP headers in the request. If not defined, no attributes are sent as headers. 
Also any dynamic properties set will be sent as headers. The dynamic property 
key will be the header key and the dynamic property value will be interpreted 
as expression language will be the header value.</td></tr><tr><td 
id="name">Basic Authentication Username</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The username to be used by the 
client to authenticate against the Remote URL.  Cannot include control 
characters (0-31), ':', or DEL (127).</td></tr><tr><td id="name">Basic 
Authentication Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The password to be used by the 
client to authenticate against the Remote URL.<br/><strong>Sensiti
 ve Property: true</strong></td></tr><tr><td id="name">Proxy Host</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully qualified hostname or IP address of the proxy server</td></tr><tr><td 
id="name">Proxy Port</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The port of the proxy 
server</td></tr><tr><td id="name">Put Response Body In Attribute</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
set, the response body received back will be put into an attribute of the 
original FlowFile instead of a separate FlowFile. The attribute key to put to 
is determined by evaluating value of this property. <br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Max Length To Put 
In Attribute</td><td id="default-value">256</td><td 
id="allowable-values"></td><td id="description">If routing the response body to 
an attribute of the original (by setting the "Put r
 esponse body in attribute" property or by receiving an error status code), the 
number of characters put to the attribute value will be at most this amount. 
This is important because attributes are held in memory and large attributes 
will quickly cause out of memory issues. If the output goes longer than this 
value, it will be truncated to fit. Consider making this smaller if 
able.</td></tr><tr><td id="name">Use Digest Authentication</td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether to communicate with the website using Digest 
Authentication. 'Basic Authentication Username' and 'Basic Authentication 
Password' are used for authentication.</td></tr><tr><td id="name">Always Output 
Response</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Will force a response FlowFile to be generated and routed to 
the 'Response' relationship regar
 dless of what the server status code received is or if the processor is 
configured to put the server response body in the request attribute. In the 
later configuration a request FlowFile with the response body in the attribute 
and a typical response FlowFile will be emitted to their respective 
relationships.</td></tr><tr><td id="name">Trusted Hostname</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Bypass the normal truststore hostname verifier to allow the 
specified remote hostname as trusted. Enabling this property has MITM security 
implications, use wisely. Will still accept other connections based on the 
normal truststore hostname verifier. Only valid with SSL (HTTPS) 
connections.</td></tr><tr><td id="name">Add Response Headers to Request</td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Enabling this property saves all the response headers to the 
original request. This
  may be when the response headers are needed but a response is not generated 
due to the status code received.</td></tr></table><h3>Dynamic Properties: 
</h3><p>Dynamic Properties allow the user to specify both the name and value of 
a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">Header Name</td><td id="value">Attribute Expression 
Language</td><td>Send request header with a key matching the Dynamic Property 
Key and a value created by evaluating the Attribute Expression Language set in 
the value of the Dynamic Property.<br/><strong>Supports Expression Language: 
true</strong></td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>Original</td><td>The
 original FlowFile will be routed upon success (2xx status codes). It will have 
new attributes detailing the success of the 
request.</td></tr><tr><td>Failure</td><td>The original FlowFile will be routed 
on any
  type of connection failure, timeout or general exception. It will have new 
attributes detailing the request.</td></tr><tr><td>Retry</td><td>The original 
FlowFile will be routed on any status code that can be retried (5xx status 
codes). It will have new attributes detailing the request.</td></tr><tr><td>No 
Retry</td><td>The original FlowFile will be routed on any status code that 
should NOT be retried (1xx, 3xx, 4xx status codes).  It will have new 
attributes detailing the request.</td></tr><tr><td>Response</td><td>A Response 
FlowFile will be routed upon success (2xx status codes). If the 'Output 
Response Regardless' property is true then the response will be sent to this 
relationship regardless of the status code received.</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>invokehttp.status.code</td><td>The
 status code that is returned</td></tr><tr><td>invokehttp.stat
 us.message</td><td>The status message that is 
returned</td></tr><tr><td>invokehttp.response.body</td><td>In the instance 
where the status code received is not a success (2xx) then the response body 
will be put to the 'invokehttp.response.body' attribute of the request 
FlowFile.</td></tr><tr><td>invokehttp.request.url</td><td>The request 
URL</td></tr><tr><td>invokehttp.tx.id</td><td>The transaction ID that is 
returned after reading the 
response</td></tr><tr><td>invokehttp.remote.dn</td><td>The DN of the remote 
server</td></tr><tr><td>user-defined</td><td>If the 'Put Response Body In 
Attribute' property is set then whatever it is set to will become the attribute 
key and the value would be the body of the HTTP 
response.</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>InvokeHTTP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>An HTTP client 
processor which can interact with a configurable HTTP Endpoint. The destination 
URL and HTTP Method are configurable. FlowFile attributes are converted to HTTP 
headers and the FlowFile contents are included as the body of the request (if 
the HTTP Method is PUT or POST).</p><h3>Tags: </h3><p>http, https, rest, 
client</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, whether a 
property supports the <a href="../../html/expression-language-guide.html">NiFi 
Expression Language</a>, and whether a property is considered "sensitive", 
meaning that its value will be encrypted. Before entering a value in a 
 sensitive property, ensure that the <strong>nifi.properties</strong> file has 
an entry for the property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>HTTP 
Method</strong></td><td id="default-value">GET</td><td 
id="allowable-values"></td><td id="description">HTTP request method (GET, POST, 
PUT, DELETE, HEAD, OPTIONS). Arbitrary methods are also supported. Methods 
other than POST and PUT will be sent without a message 
body.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Remote URL</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Remote URL which will be 
connected to, including scheme, host, port, path.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">SSL Context 
Service</td><td id="default-value"></td><td id="allowable-values"><s
 trong>Controller Service API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
 id="description">The SSL Context Service used to provide client certificate 
information for TLS/SSL (https) connections.</td></tr><tr><td 
id="name"><strong>Connection Timeout</strong></td><td id="default-value">5 
secs</td><td id="allowable-values"></td><td id="description">Max wait time for 
connection to remote service.</td></tr><tr><td id="name"><strong>Read 
Timeout</strong></td><td id="default-value">15 secs</td><td 
id="allowable-values"></td><td id="description">Max wait time for response from 
remote service.</td></tr><tr><td id="name"><strong>Include Date 
Header</strong></td><td id="default-value">True</td><td 
id="allowable-values"><ul><li>True</li><li>False</li></ul></td><td 
id="description">Include an RFC-2616 Date header in the 
request.</td></tr><tr><td id="name"><stro
 ng>Follow Redirects</strong></td><td id="default-value">True</td><td 
id="allowable-values"><ul><li>True</li><li>False</li></ul></td><td 
id="description">Follow HTTP redirects issued by remote 
server.</td></tr><tr><td id="name">Attributes to Send</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Regular expression that defines which attributes to send as 
HTTP headers in the request. If not defined, no attributes are sent as headers. 
Also any dynamic properties set will be sent as headers. The dynamic property 
key will be the header key and the dynamic property value will be interpreted 
as expression language will be the header value.</td></tr><tr><td 
id="name">Basic Authentication Username</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The username to be used by the 
client to authenticate against the Remote URL.  Cannot include control 
characters (0-31), ':', or DEL (127).</td></tr><tr><td id="name">Basic Authenti
 cation Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The password to be used by the 
client to authenticate against the Remote URL.<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Proxy Host</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully qualified hostname or IP address of the proxy server</td></tr><tr><td 
id="name">Proxy Port</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The port of the proxy 
server</td></tr><tr><td id="name">Put Response Body In Attribute</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
set, the response body received back will be put into an attribute of the 
original FlowFile instead of a separate FlowFile. The attribute key to put to 
is determined by evaluating value of this property. <br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Max 
 Length To Put In Attribute</td><td id="default-value">256</td><td 
id="allowable-values"></td><td id="description">If routing the response body to 
an attribute of the original (by setting the "Put response body in attribute" 
property or by receiving an error status code), the number of characters put to 
the attribute value will be at most this amount. This is important because 
attributes are held in memory and large attributes will quickly cause out of 
memory issues. If the output goes longer than this value, it will be truncated 
to fit. Consider making this smaller if able.</td></tr><tr><td id="name">Use 
Digest Authentication</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether to communicate with the website using Digest 
Authentication. 'Basic Authentication Username' and 'Basic Authentication 
Password' are used for authentication.</td></tr><tr><td id="name">Always Output 
Response</td><td id="default-va
 lue">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Will force a response FlowFile to be generated and routed to 
the 'Response' relationship regardless of what the server status code received 
is or if the processor is configured to put the server response body in the 
request attribute. In the later configuration a request FlowFile with the 
response body in the attribute and a typical response FlowFile will be emitted 
to their respective relationships.</td></tr><tr><td id="name">Trusted 
Hostname</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Bypass the normal truststore hostname verifier to allow the 
specified remote hostname as trusted. Enabling this property has MITM security 
implications, use wisely. Will still accept other connections based on the 
normal truststore hostname verifier. Only valid with SSL (HTTPS) 
connections.</td></tr><tr><td id="name">Add Response Headers to Request</td><td 
id=
 "default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Enabling this property saves all the response headers to the 
original request. This may be when the response headers are needed but a 
response is not generated due to the status code received.</td></tr><tr><td 
id="name"><strong>Content-Type</strong></td><td 
id="default-value">${mime.type}</td><td id="allowable-values"></td><td 
id="description">The Content-Type to specify for when content is being 
transmitted through a PUT or POST. In the case of an empty value after 
evaluating an expression language expression, Content-Type defaults to 
application/octet-stream<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Use Chunked 
Encoding</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">When POST'ing or PUT'ing content set this property to true in 
order to
  not pass the 'Content-length' header and instead send 'Transfer-Encoding' 
with a value of 'chunked'. This will enable the data transfer mechanism which 
was introduced in HTTP 1.1 to pass data of unknown lengths in 
chunks.</td></tr><tr><td id="name">Penalize on "No Retry"</td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Enabling this property will penalize FlowFiles that are routed 
to the "No Retry" relationship.</td></tr></table><h3>Dynamic Properties: 
</h3><p>Dynamic Properties allow the user to specify both the name and value of 
a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">Header Name</td><td id="value">Attribute Expression 
Language</td><td>Send request header with a key matching the Dynamic Property 
Key and a value created by evaluating the Attribute Expression Language set in 
the value of the Dynamic Property.<br/><strong>Supports Ex
 pression Language: true</strong></td></tr></table></p><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>Original</td><td>The
 original FlowFile will be routed upon success (2xx status codes). It will have 
new attributes detailing the success of the 
request.</td></tr><tr><td>Failure</td><td>The original FlowFile will be routed 
on any type of connection failure, timeout or general exception. It will have 
new attributes detailing the request.</td></tr><tr><td>Retry</td><td>The 
original FlowFile will be routed on any status code that can be retried (5xx 
status codes). It will have new attributes detailing the 
request.</td></tr><tr><td>No Retry</td><td>The original FlowFile will be routed 
on any status code that should NOT be retried (1xx, 3xx, 4xx status codes).  It 
will have new attributes detailing the 
request.</td></tr><tr><td>Response</td><td>A Response FlowFile will be routed 
upon success (2xx status codes). If the 'Output Response R
 egardless' property is true then the response will be sent to this 
relationship regardless of the status code received.</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>invokehttp.status.code</td><td>The
 status code that is 
returned</td></tr><tr><td>invokehttp.status.message</td><td>The status message 
that is returned</td></tr><tr><td>invokehttp.response.body</td><td>In the 
instance where the status code received is not a success (2xx) then the 
response body will be put to the 'invokehttp.response.body' attribute of the 
request FlowFile.</td></tr><tr><td>invokehttp.request.url</td><td>The request 
URL</td></tr><tr><td>invokehttp.tx.id</td><td>The transaction ID that is 
returned after reading the 
response</td></tr><tr><td>invokehttp.remote.dn</td><td>The DN of the remote 
server</td></tr><tr><td>user-defined</td><td>If the 'Put Response Body In 
Attribute' property is se
 t then whatever it is set to will become the attribute key and the value would 
be the body of the HTTP response.</td></tr></table></body></html>
\ No newline at end of file


Reply via email to