HTTP & HTTPS

Support for file transfers based on HTTP, functioning as both a server and a client. This capability allows for flexible and secure data exchange, accommodating various protocols and workflows within a single solution.

HTTP Server Functionality ​

As an HTTP server, SFTPPlus allows external parties to connect and exchange files. It supports a range of methods and protocols to fit different use cases.

  • Simple Transfers: It handles basic file exchange using standard HTTP GET and PUT methods. These operations enable straightforward file downloads and uploads.
  • REST API: The platform can expose a RESTful API for file management, allowing programmatic access to files. This is useful for applications that need to integrate file transfers into their workflows using modern API standards.
  • WebDAV: SFTPPlus includes support for WebDAV (Web-based Distributed Authoring and Versioning), which extends HTTP to allow for collaborative authoring and file management. Clients can browse, copy, move, and edit files on the server.
  • AS2 Protocol: For secure business-to-business (B2B) transactions, SFTPPlus supports AS2 (Applicability Statement 2). AS2 is used for securely transmitting EDI (Electronic Data Interchange) documents and other business data over HTTP or HTTPS. It includes features like digital signatures, encryption, and non-repudiation with Message Disposition Notifications (MDNs).

All server-side HTTP communications are protected by TLS, ensuring data confidentiality and integrity. The server can also be deployed behind a load balancer, with support for X-Forwarded-For headers or ProxyProtocol2 to maintain visibility of the original client IP address.

Customize HTTP response headers ​

Administrators can add custom headers to every HTTP or HTTPS response. The configuration can also replace a standard header, including the Server header, with an organization-specific or generic value.

Replacing this header obscures the product identity and version exposed to remote clients. It also supports white-labelled endpoints and security policies that limit software fingerprinting.

Transfer files using the HTTP API ​

The HTTPS service provides a RESTful JSON API for listing and managing files. For example, this cURL request authenticates as api-user and returns a JSON listing of the /reports/ folder:

shell
curl \
    --user api-user \
    --header 'Accept: application/json' \
    https://mft.example.com:10443/home/reports/

cURL asks for the account password without placing it in the command history. The same API supports file downloads, uploads, folder creation, and deletion, subject to the account's permissions. See the HTTP file transfer service API documentation for the available operations, authentication methods, and response formats.

HTTP Client Functionality ​

SFTPPlus can also act as an HTTP client, connecting to remote servers to automate file transfers. This is a key feature for creating a "bridge" between different systems.

It enables automated file downloads from any HTTP page. For instance, SFTPPlus can be configured to fetch the content of a web page and store the content as a local file or forward it to an SFTP server or a cloud storage service like Azure Blob

It can get files for local disk or remote server and push them to an AS2 server.

This simplifies complex data flows by centralizing the transfer process within the SFTPPlus platform, eliminating the need for manual scripting or separate client applications.

Generate an HTTP response file from a local request file ​

SFTPPlus supports HTTP pull transfers for APIs that generate a file in response to a request. A file created in the configured source directory triggers the transfer. SFTPPlus uses the content of that local file as the request payload, sends it to the remote HTTP service, and stores the response as the destination file.

Both POST and PUT requests are supported. This file-driven workflow can connect a local process that generates request data with an HTTP service that returns the final file, without requiring a separate transfer script.

HTTPS Server and Load Balancers ​

SFTPPlus can function as an HTTP server and is designed to operate seamlessly behind a load balancer, both TCP and application load balancer. To accurately identify the original source of a request, SFTPPlus has native support for X-Forwarded-For headers and ProxyProtocol2.

All HTTP transfers are protected by TLS, ensuring secure communication. For authentication, SFTPPlus supports username and password-based methods, along with advanced options like mutual TLS authentication, which verifies both the client and server.

HTTP Client Transfers for Bridging Systems ​

The HTTP and AS2 client transfer capabilities of SFTPPlus are highly effective for creating a bridge between different systems. This feature allows for the seamless movement of files from various sources to other HTTP or AS2 servers.

For example, you can transfer files from an SFTP server, Web server, Azure Blob, SharePoint Online, or an email server to a AS2 destination server. This bridging functionality simplifies complex workflows and centralizes file transfer management across disparate systems.

Support and consultancy from experts ​

SFTPPlus is Drummond Certified, a certification that validates the product's interoperability and adherence to AS2 standards.

If you are looking to implement secure HTTP transfers or migrate from legacy systems, the SFTPPlus support team is ready to help. With over 20 years of experience, our team has assisted numerous customers in deploying secure transfer solutions and transitioning from older protocols like FTP to modern HTTP or cloud-based systems.

Get in touch with our experts to discuss your specific needs and ensure a smooth implementation.