Aspera Connect Browser Plug-in 3.6.5 Release Notes
Product Release: February 5, 2016
Release Notes Updated: February 8, 2017
- Connect now supports the Microsoft Edge browser.
- A bug was fixed in which Chrome warned of "mixed content," and the HTTPS lock showed a warning.
- A bug was fixed that could force the Connect window to the front on certain new OS X client hosts.
- The Connect application now complies with Apple security best practices.
- If you host the Connect SDK on your own servers, it is loaded from there.
- A bug was fixed that limited the number of concurrent instances of Connect on Windows.
ISSUES FIXED IN THIS RELEASE
#34355 - [Chrome only] Connect formerly used ports in the 33003 range for local host communication, but now uses 43003 ports. If you use an antivirus program for local host traffic, you should configure it to allow ports 43003-43012. Other browsers are unaffected, and continue to use ports in the 33003 range.
#33861 - [Firefox only] Because of a change in Firefox's requirements, Connect no longer includes a web installer for this browser. Instead, to use Connect with Firefox, you can download the installer and then install Connect.
#33619 - [OS X only] The Connect application now complies with the Apple best practices for security.
#32839 - [Windows only] There was an issue limiting the number of simultaneous Connect users on the same computer. The maximum number of unique users on the client machine is now 10.
#32726- For transfer servers that host the Connect SDK locally, the default behavior has changed as to which location is used. Connect now uses the location specified in the web application (Faspex, Shares, Console, or a custom app) to load the API files, installer code, and plugins (if an upgrade is needed). If these files are not found on the web application server, the production server (CloudFront) is used. This change was made to improve the robustness of local serving of the Connect SDK package.
#32631 - [OS X only] The Connect window can incorrectly gain keyboard focus, displaying in front of all other applications.
#32558 - [OS X only] Chrome can present an unnecessary confirmation dialog.
#30299 - Chrome issued a warning icon and log messages about "mixed HTTP and HTTPS content."
- OS: Windows 7, 8, or 10. Windows Server 2008 r2 or 2012.
- Browser: Internet Explorer 8 and 9 (with limitations), Internet Explorer 10-11, Firefox
27-43, Chrome 32-47, or Microsoft Edge (EdgeHTML versions 12.10240 and 13.10586).
Note: Drag-and-drop is not supported on the Edge browser at this time.
- OS: OS X 10.6 (with limitations) through 10.11
- Browser: Safari 6-9, Firefox 27-43, or Chrome 32-47
PREVIOUS RELEASE NOTES
- Connect 3.6.1 Release Notes
- Connect 3.6.0 Release Notes
- Connect 3.5.3 Release Notes
- Connect 3.5.2 Release Notes
- Connect 3.5.1 Release Notes
- Connect 3.4.2 Release Notes
- Connect 3.3.4 Release Notes
- Connect 3.3.3 Release Notes
- Connect 3.1.4 Release Notes
- Connect 3.1.2 Release Notes
- Connect 3.1.1 Release Notes
- Connect 3.1.0 Release Notes
- Connect 3.0.1 Release Notes
- Connect 3.0.0 Release Notes
md5: 52d21c98f177f24aabb6886ca0507531 sha1: 73a8c73fa6dcc000a7618247cd8010f371cc6c7e
md5: 4313454ceba4c0150b89a9f8f9c0c20e sha1: 67fccb3356e09cebeb87cd713829a7a8fd120a80
- IBM Aspera Connect 3.6.5 User Guide (Windows) [English]
- IBM Aspera Connect 3.6.5 User Guide (Windows) [Spanish]
- IBM Aspera Connect 3.6.5 User Guide (Windows) [French]
- IBM Aspera Connect 3.6.5 User Guide (Windows) [Japanese]
- IBM Aspera Connect 3.6.5 User Guide (Windows) [Chinese]
- #34277 - [OS X only] If your system has a proxy configured, you must install Connect with administrator privileges.
- #33004 - [Windows 10 only] When filenames contain Nepali script, they do not display correctly in Connect's Transfers window. Other Unicode characters do display correctly.
- #32938 - [OS X only] If an administrator has a single-user Connect installation,
standard users on that computer are blocked from using Connect. To address this, either
- Have the administrator perform a system-wide installation (instead of a single-user
- Have the standard users perform their own single-user installations.
- Have the administrator perform a system-wide installation (instead of a single-user installation).
- #32908 - Connect can display an unnecessary proxy configuration dialog.
- #32825 - [OS X 10.6 only] On OS X 10.6 with Firefox 41, the Connect browser plug-in crashes when pages are loaded that use it.
- #32716 - In Chrome 45 and higher, the browser may not detect that a previous version of Connect is installed. You can follow the steps to download and install Connect.
- #32446 - [Windows only] If you perform a system-wide installation of Connect, Aspera recommends that you not use the built-in Administrator account for this installation. The built-in Administrator account includes privilege settings that are too high, resulting in various issues in Connect capabilities. Most importantly, your users will not be able to drag and drop files in the Connect interface, in any browser. Instead of the built-in Administrator account, Aspera recommends that you use a different administrator account for system-wide installation.
- #32258 - [Windows only] In Internet Explorer, drag-and-drop actions work for files, but not for folders.
- #32159 - [Windows 10 only] In Aspera Shares 1.9.1 or older, the button to install Connect may not display correctly. To install Connect in these cases, download the Connect installer from http://downloads.asperasoft.com/ and then run it.
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.