Benefits

• Efficient debugging experience: Without Catalyst Tunneling, debugging non-HTTPS functions like Cron and Event or Integration functions in the development environment was an inconclusive task. You didn’t have the freedom to set your preferred break points in your code file and debug them as you would Basic I/O and Advanced I/O functions. Now, using Tunneling, you can trigger Cron, Event, and Integrations functions at will and examine every code line with absolute ease.

• No limitation on reverse-proxy providers: Catalyst Tunneling can be used with any reverse-proxy providers of your choice. While there is no limitation to which reverse-proxy provider you can use, we recommend that you use the services of trusted reverse-proxy providers. You can find detailed steps on how to configure Tunneling URL using some of the more popular reverse-proxy providers in this section.

• No IDE restrictions: If your IDE allows you to configure a debugger, with Catalyst Tunneling, you can directly use it to debug your non-HTTPS and Integration functions. This help documentation also contains specific steps on configuring the debuggers of some of the commonly used IDEs.

• Manage Tunneling from the console: You can enable, disable, and select multiple functions for tunneling directly in the console. The Catalyst console will also automatically disable tunneling after 24 hrs if you do not disable the tunneling process. You also have the option of updating your selection of non-HTTPS and Integration functions that you need to tunnel.