====== HTTP receive channel ======

The HTTP receive channel enables the connection to services that communicate via HTTP protocol. eBiss acts as a server.
Messages are transferred to the receiving channel via HTTP POST request, received by the receiving channel and placed in the specified messagebox (incoming).

Special characters are correctly handled in the HTTP header. So that for example the file name or the subject with sprecial characters
are corretly transmitted. This is possible in a eBiss to eBiss case and also from extern. In case of an external send the
header must be 'UrlEncoded' and **before** the first encoded header the following header must be inserted:
  * X-Pranke-UrlDecode: TRUE


==== Properties ====

^GENERATED src="eBiss.Data.Resources.HttpReceiveChannel" changed=""^^
^Properties^^
^Name^Description^
|**Name**|The name of the channel|
|**Channel type name**|The Type of the channel|
|**Message direction**|For receive channels the direction of the received message (but require also for send channels)|
|**Message box**|The message box|
|**Public**|True if the channel should be visible in the sub node|
|**URL**|Not relevant for most applications. This URI is specified externally for certain calls.|
|**Authentication**|Type of authentication: None, Fix (configured in the channel), Sender (depending on the message direction using the HTTP Auth address of the system or trading partner)|
|**Username**|The user to be used for the login|
|**Password**|The password|
|**AuthenticateDomain**|Authentication Domain|
|**SSL option**|Which TLS version should be used.|
|**SSL certificate**|File containing the own private certificate for SSL, usually a p12 file.|
|**SSL password**|Password for the SSL certificate|
|**SSL subject**|
|**SSL expiration date**|
|**Change logs**|The changes to the element are logged. The logging is activated in the [[en:hauptmenue:einstellungen:systemeinstellungen]], which is possible if a versioning license is available.|
^Properties (advanced)^^
^Name^Description^
|**Sender validation**|How the sender address should be validated|
|**Default sender**|The default sender|
|**Recipient validation**|How the recipient  address should be validated|
|**Default recipient**|The default recipient|
|**Immediate retries**|Retries, used by send channels. For some receive channels, the number of pickup attempts.|
|**Auto uncompress**|Check if receipt data are compressed and then uncompress them|
|**Proxy behaviour**|If the URL accessed by the client is to be evaluated as a node path or as a local partner address.|
|**Process multipart messages**|Messages of the Content-Type=multipart are to be processed.|
|**Allow multiple messages**|Accept multiple messages in one session and allow 'Keep-Alive'.|
|**Use defined responses**|Activate this option to return 'Negative response' or 'Positive response'.|
|**Positive response**|Positive HTTP response see above.|
|**Negative response**|Negative HTTP response (see above)|
|**Use SSL**|Activate this for HTTPS|