Currently, VSN client just manages unencrypted HTTP requests and responses - sending some to VSN server and some directly to the origin server. Now, the VSN server is publicly accessible. In some cases, a VSN server could be within a closed enterprise network, and so the VSN client might need to establish a VPN connection to access the VSN server. Hence, the VSN client needs to made compatible to support a simulated network interface which can participate in setting up VPN connections. Then, some requests go to the VSN server through the encrypted VPN channel, and some directly go to the origin server unencrypted.

Note: See TracRoadmap for help on using the roadmap.