Configure HST Server
in the GUI
The following references describe the server settings that can be configured in the HST Server GUI. Not all
settings are available in the GUI; some must be set by using the command line or directly editing
the HST Server configuration
file, aspera.conf .
Docroot and File Permission Configuration Docroot configuration options include the docroot and file permissions. The absolute path, or docroot, is the area of the file system that is accessible to an Aspera transfer user. The default empty value allows access to the entire file system. You can set one global docroot and then further restrict access to the file system by group or individual user. Authorization Configuration Authorization configuration options include connection permissions, token key, and encryption requirements.Server-Side Encryption at Rest (EAR) Bandwidth Configuration Bandwidth configuration options include target transfer rates, transfer policies, and assigning vlinks to control aggregate bandwidth usage.Controlling Bandwidth Usage with Virtual Links (GUI) groups, or sets of specific users, set up a virtual link (Vlink).Network Configuration Network configuration options include the network IP, port, and socket buffer settings.File Handling Configuration File Handling configuration options include file block size, overwrite rules, symbolic link handling, and filtering patterns.Configuring Inline File Validation in the GUI the Aspera server GUI or aspera.conf .Configuring Filters to Include and Exclude Files Reporting Checksums Transfer Server Configuration HST Server uses asperacentral to handle transfer requests from Aspera clients. You can configure server properties and behavior in the Transfer Server options, including specifying the address, enabling persistent storage, and controlling how to handle empty files.