HTTP/S

The Hypertext Transfer Protocol (HTTP) is an application layer protocol, designed within the framework of the Internet protocol suite, for distributed, collaborative, hypermedia information systems. HTTP functions as a request–response protocol in the client–server computing model. A web browser, for example, may be the client and EFT is the server. The client submits an HTTP request message to the server. The server, which provides resources such as HTML files and other content, or performs other functions on behalf of the client, returns a response message to the client. The response contains completion status information about the request and may also contain requested content in its message body.

Hypertext Transfer Protocol Secure (HTTPS) is an extension of HTTP, used for secure communication over a network for authentication, privacy protection, and integrity of the transferred data while in transit. Unlike HTTP, HTTPS protects against man-in-the-middle attacks, and provides bidirectional encryption of communications between a client and server. HTTPS encrypts all message contents, including the HTTP headers and the request/response data.

The HTTP and HTTPS protocols can be enabled/configured on an EFT Site and inherited by the Settings Templates and user accounts. (You can then configure the Settings Templates and user accounts differently, if needed.) The topics below provide the procedures for configuring HTTP/S settings on Sites, Settings Templates, and user accounts.

• HTTP and HTTPS Overview

• Configuring HTTP or HTTPS Transfers

• Customizable HTTP Error Messages

• Enable HSTS

• Enabling User Access to the Web Transfer Client

• OCSP

• Redirecting HTTP to HTTPS

• Using WebDAV with EFT

• Invoke Web Service Action