-
Type: Task
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Aspera Connector
Currently with httpclient, filenames with special character will fail to interact with Aspera due to parsing issue
This can be fixed with ISO8859-1 enabled, however the same needs to be validated and incorporated in all other instances whenever Aspera Rest APIs are being invoked.
- is related to
-
NXP-31420 Parse error in AsperaNodeServiceImpl
- Resolved