Currently, we have a Java applet called ThinLincClientVerifier in order to verify if the client is installed, and (if not) initiate the installation. However, Java Applets are considered legacy nowadays. I haven't found any numbers, but my guess is that many desktop browsers lacks support for Java applets. Thus, it would be great if we could find some other solution. It doesn't have to be perfect - the applet doesn't run on all machines either.
One idea would be to define a custom protocol handler. However, verifying if a certain protocol handler is defined/available or not is very difficult in todays browsers.
A few unsorted links:
Perhaps we need to keep the Java applet solution for now.
Chrome does not support Java plugins through NPAPI from Chrome 45 and onwards, says https://java.com/en/download/faq/chrome.xml
We don't see any obvious solutions to this problem and Java is pretty dead now. It is acceptable to remove the functionality for now.
Tester should check:
- Basic functionality of tlclient.cgi and cgitest.html
- The "redirto" setting of tlclient.cgi
- That there isn't any remnants of the applet in the source tree
✓ Basic functionality of tlclient.cgi and cgitest.html
✓ The "redirto" setting of tlclient.cgi (Note *)
✓ That there isn't any remnants of the applet in the source tree
* Note that "redirto" never works from cgitest.html anymore now. Previously it didn't work when you disabled the app verifier. I choose to not create a bug for this. The "redirto" setting works well when using tlclient.cgi with cgi parameters.