SFTPPlus Release 3.44.0
- ⬅ All articles
- 🗂 Categories
- 🔖 ftp (1)
- 🔖 infrastructure (3)
- 🔖 privacy (1)
- 🔖 compliance (1)
- 🔖 client-side (1)
- 🔖 general (84)
- 🔖 blog (6)
- 🔖 press (2)
- 🔖 australia (1)
- 🔖 client (17)
- 🔖 release (81)
- 🔖 article (14)
- 🔖 security (24)
- 🔖 server (19)
- 🗄 Archive
- 📌 2001 (3)
- 📌 2005 (1)
- 📌 2006 (1)
- 📌 2007 (1)
- 📌 2008 (1)
- 📌 2012 (1)
- 📌 2013 (3)
- 📌 2014 (13)
- 📌 2015 (20)
- 📌 2016 (23)
- 📌 2017 (14)
- 📌 2018 (38)
- 📌 2019 (17)
Thu 24 January 2019 | general release
We are announcing the latest release of SFTPPlus version 3.44.0.
New Features
- It is now possible to configure the name associated to the sender email address in the email client resource. [#3069]
- It is now possible for file transfer users to change the password associated with their accounts via the HTTP / HTTPS protocols. [server-side][http][https] [#5128]
- It is now possible to configure an email sender event handler with CC and BCC fields. [#5158]
- It is now possible to monitor OS resources used by SFTPPlus, and trigger an event when their usage hits certain configurable limits. This feature is not available on HP-UX, Windows XP and Windows Server 2003. [#5175]
- Alpine Linux 3.7 on X86_64 is now a supported platform. [#5179]
- It is now possible to schedule a transfer based on week days. [client-side][#5184]
Defect Fixes
- The HTTP/HTTPS file transfer service login page is now accessible in HTML format for Internet Explorer in compatibility mode. [http][https][server-side] [#5188]
Deprecations and Removals
- The URL of the login page used by the HTTP/HTTPS file transfer service was moved from /login to /__chsps__/login. [server-side][http][https] [#5128]
- Support for Alpine Linux 3.6 on X86_64 was removed. [#5179]
- Event with ID 60019 emitted when a transfer has invalid schedule configuration was removed and replaced with the generic event ID. [#5184]
- The HTTP/HTTPS file transfer API now requires an explicit Accept: application/json header in order to use the JSON variant of the API. Otherwise, it will default to the HTML/WebDAV variant. [http][https][api][server-side] [#5188]
You can check the full release notes here.