www.cendio.com
Bug 4521 - Remove ThinLincClientVerifier applet
: Remove ThinLincClientVerifier applet
Status: CLOSED FIXED
: ThinLinc
Client platforms
: trunk
: PC Unknown
: P2 Normal
: 4.9.0
Assigned To:
:
:
:
: 6082
  Show dependency treegraph
 
Reported: 2013-01-23 12:49 by
Modified: 2018-03-05 16:55 (History)
Acceptance Criteria:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From cendio 2013-01-23 12:49:09
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.
------- Comment #1 From cendio 2013-01-24 08:29:54 -------
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. 

Of course, the best solution would be if it was possible to check if our
special mime type is defined, using Javascript instead of the current solution.
As far as I can tell, this is impossible in all (?) browsers. 

A few unsorted links:

http://stackoverflow.com/questions/2171809/check-if-a-browser-supports-a-specific-mime-type
http://stackoverflow.com/questions/836777/how-to-detect-browsers-protocol-handlers
http://browserspy.dk
http://stackoverflow.com/questions/5034571/how-to-tell-whether-a-protocol-is-valid-in-javascript?lq=1
https://gist.github.com/2662899
http://stackoverflow.com/questions/2872090/how-to-check-if-a-custom-protocol-supported

Perhaps we need to keep the Java applet solution for now.
------- Comment #2 From cendio 2016-05-19 12:23:48 -------
Chrome does not support Java plugins through NPAPI from Chrome 45 and onwards,
says https://java.com/en/download/faq/chrome.xml
------- Comment #3 From cendio 2016-11-08 14:05:28 -------
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.
------- Comment #5 From cendio 2018-02-26 13:17:13 -------
Tester should check:

 - Documentation
 - 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
------- Comment #7 From cendio 2018-03-05 16:55:58 -------
Looks ok.

 ✓ Documentation
 ✓ 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.