View Single Post
Old 03-22-2019, 06:07 PM
berdmann berdmann is offline
VanDyke Technical Support
Join Date: Aug 2017
Posts: 253
Hi exyl3d,

Firefox is a red herring because it keeps its own URL Schema to App Handler mappings, rather than using the OS-mapped handlers.

Logically, it would seem that if the only remaining variable is a newer version of Chrome, that perhaps Chrome is causing the problem -- after all, SecureCRT is happily running unaware of Chrome being updated. However, sometimes reality can defy logic

If you set iTerm as the default telnet handler, and then upgrade Chrome, does Chrome continue to use iTerm as the default telnet handler without interruption, or do you have to do the same thing with iTerm as with SecureCRT?

VanDyke Software
Technical Support
(505) 332-5730
Reply With Quote