...
Add feature to sign .nexaweb files with a user key pair | |
Proxy authentication fails in customer environment using Nexaweb Launcher 1.4.3. | |
Allow proxy information to be re-entered if proxy authentication fails. | |
Improvements regarding the original data of the signature target(Parameters of .nexaweb file can be overwritten) | |
NXPSR-11258 | Cookie is not inherited when accessing from getdown |
NXPSR-11260 | Launcher makes an unnecessary request to getdown.txt |
NXPSR-11261 | The request from ClientClassLoader does not contain cookies. |
When using Nexaweb Launcher, there are requests for unnecessary class files. | |
Should only use proxy if the direct connection fails. | |
[Compatibility] Nexaweb Launcher 1.4.4 has a different priority for the JVM used by the Standalone Client. | |
NXPSR-11270 | Proxy.txt file is not removed when uninstalling Nexaweb launcher. |
Launcher application does not start when there is issue with getting java version with win32 | |
NXPSR-11274 | [Compatibility] Launcher 1.4.5, need to work on platform 4.5.70 -72 versions |
NXPSR-11247: Add feature to sign .nexaweb files with a user key pair
...