This is a bugfix release.
Users were reporting that it is still not possible to use Aspera through their proxy implementation. Client indicates problem points in AsperaIterator and AsperaBrowseFilesIterator now fixed.
A new retry button is added during the upload if one or many files inside the folder are failing.
This is a fix. When creating one transfer, if we add a couple of folders and when editing the transfer and put some common metadata for both folders.
Wait till they are uploaded in transient. Click on edit metadata. Change metadata for one folder. Complete transfer
Wait for the transfer to be completed. After completion Check metadata for all the files under the folder whose metadata was changed.
We were seeing the common old metadata. But now we can see the new metadata which was given.
As a part of NXP-31290 & NXP-31356, (to enable proxy support) all Jersey Client instance has been replaced with httpclient.
Due to this change, the default encoding config seems to have started rejecting filenames with special character, leading to the parse issue at Aspera Side. Applied the fix on this a the error is fixed.
During Retry, Invoking Aspera APIs might lead to failure as Aspera stores information related to a transfer only for a limited time. (24 hrs)
Since the info needed from Aspera is already processed during complete transfer, We can extract and store that information inside Transfer and skip any future Aspera API calls for the same transfer during retry.