EBICS Host: HTTP Tab

HTTP/HTTPs
Only HTTP/s is allowed for EBICS; therefore, it is pre-selected and cannot be changed. However, to verify that the server name in the received SSL server certificate matches the connected server name, select Check certificate server name.
Check certificate server name
Verifies that the server name in the received SSL server certificate matches the server name actually connected to.
Method
Use POST for both the PUT and GET commands since POST is used exclusively within the context of EBICS.
Path
The bank server's resource path. Given the URL provided by your banking partner in the form https://remote-host:port/resource-path?optional-parameters, the bolded portion in this field should be entered. Note that the beginning slash ("/") is required.
Parameters
Specify any optional URL parameters. By default, no parameters are specified for EBICS messages. If parameters are required, you must obtain them from your banking partner when the relationship is established. Given the URL provided by the banking partner in the form https://remote-host:port/resource-path?optional-parameters the bolded portion in this field should be entered. 
For syntax and rules on specifying HTTP parameters, see HTTP Configuration section. Note that you cannot specify a parameter that matches an EBICS PUT/GET reserved parameter (for example, OrderType).
Headers
Specify values to override any default headers or add new, custom headers. When overriding default headers, make sure they meet the requirements of the EBICS specification. The VersaLexCleo HarmonyCleo VLTraderCleo LexiCom EBICS client will, by default, generate the following headers on all generated HTTP requests: 
  • Host header (for example, Host: bank01.bank.com:443)
  • Content-type header, with the name parameter if applicable (for example, Content-Type: text/xml; name=cust01.pain.001.001.02)
  • Content-Length header (for example, Content-length:1000)
The VersaLexCleo HarmonyCleo VLTraderCleo LexiCom EBICS client will in turn honor the following headers on all generated HTTP responses:
  • Content-type header, with the name parameter if applicable (for example, Content-type: text/xml; name=cust01.camt.053.001.02)
  • Content-Length header (for example, Content-length:1000)
  • Content-Disposition header, with the filename parameter if applicable (for example, Content-disposition: inline; filename= cust01.camt.053.001.02)