Aspera Proxy Server 1.2.1 Release Notes
- Product Release: Sep 12, 2014
- Release Notes Updated: Sep 12, 2014
This release of Aspera Proxy makes the following change and corrects issues listed below.
- Source-port filtering is now disabled by default (<src_port_filtering> is set to false). For information about source-port filtering, see the Aspera Proxy Admin Guide.
ISSUES FIXED IN THIS RELEASE
#19255 - Proxy cannot identify client via hostname.
#20261 - Proxy: ascp -A does not provide information about license validity.
#22963 - Documentation implies reverse proxy requires squash user account on the proxy machine.
#23585 - Transfers denied for user if a previous transfer from a different user is running when using a reverse proxy.
#19184 - Proxy installer does not enable IP forwarding when using restart or force-reload options with the service command. Workaround: Use start and stop to run the service.
#19185 - If you specify a directory for <log_dir>, the log file is created with 0640 permissions. As a result, not all transfers will be logged. Workaround: Once the log file has been created, change its permissions to 0660.
#19202 - Proxy does not currently support reverse proxy for web applications.
#19205 - Proxy does not support HTTP fallback.
#21288 - On some Linux platforms (for example, SUSE) the iptables-restore command is not located in /sbin but /usr/sbin. Workaround: Create a symlink in /sbin for /usr/sbin/iptables-restore.
Linux 64-bit: RedHat 6 & 7, CentOS 6 & 7, Fedora 15-20, Ubuntu 12-14, Debian 6 & 7, SLES 11, Kernel 2.4 or higher and libc version GLIB 2.3.4+.
PREVIOUS RELEASE NOTES
md5: bbf80976f6c24648559c0ff9826cdcae sha1: ee3723ea6c84127e2dda5bc67358104d17a885aeaspera-proxy-22.214.171.124571-linux-64.rpm
md5: 03e818105159ea071844b230db935942 sha1: 58df7e23a1160ca117ed32cd46f6cf243a0ecab2
For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.