Impacts on Curl Applets Due to End of Support for Internet Explorer
Microsoft has announced that it will end support for the "Internet Explorer" (IE) on June 15, 2022 (US local time).
After end of support of IE, Microsoft will no longer provide security updates, etc., and it may be affected by virus, so we recommend that you refrain from using IE on the affected OS. In order for our customers to continue using our Curl RTE products, please take the following actions regarding the Curl applet you are using.
Curl RTE supports the following two types of applets.
- Detached applet (extension: .dcurl)
Since it does not depend on the browser, no special measures need to be taken. - Applet executed in the browser (extension: .curl) * Hereafter, legacy applet
You can continue to use legacy applets in IE mode of Microsoft Edge (hereinafter, Edge).
If you do not use Edge's IE mode, you need to migrate the legacy applet to the above 1. detached applet.
How to use Edge IE mode
Edge is provided as the successor browser to IE, and legacy systems that depend on IE will continue to work with IE mode of the new Edge (version 77 or later).
For details on IE mode of Edge, please refer to the official Microsoft document.
Migrating to a detached applet
If Edge's IE mode is no longer supported, legacy applets will no longer be able to run. Therefore, please consider migrating from legacy applets to detached applets.
Impact on Embedded Browser Graphic
EmbeddedBrowserGraphic is provided as a web browser control of Curl's standard API. EmbeddedBrowserGraphic uses the Win32 API WebBrowser control (Microsoft ActiveX control), but at this time, Microsoft has not announced that the API will be discontinued. Therefore, even after Edge's IE mode support ends, it may continue to be available in a detached applet.
The next version of Curl (release date undecided) will provide a successor API to EmbeddedBrowserGraphic.
About legacy applets that use APIs related to “Browser Resident HTTP”
If you share browser-side cookies / authentication information using "Browser Resident HTTP", these functions can be used in IE mode of Edge after the end of IE support (* with restrictions), but after the end of support for IE mode of Edge, they will no longer be available.
In such cases, you will need to migrate to a detached applet as described above.
* Restriction: When implementing the SSO function between IE mode on Edge and legacy applet with the "browser-resident HTTP" function, the original system whose cookies to be inherited must also be used in IE mode on Edge.
When migrating to a detached applet, it is necessary to change the method of passing cookie information from other systems. Please refer to the following technical information site for how to deal with it: http://tech.curlap.com/cookie-hikitugi/
Please contact us if you cannot achieve the above technical information due to special technical requirements.
