Please, please, PLEASE bring back HTTPS bookmarks, but do it right this time. We have a situation where we wanted to replace an old Cisco ASA 5500 with a Sophos XG but due to the lack of support for HTTP/S bookmarks in the Clientless VPN we can no longer do that. We have been forced to find an alternative and at this point we are stuck with the ASA for now and having to place it on a port on the Sophos placed in the DMZ so the ASA can continue to be used as the method of access to an internal web server. We have setup a Web Protection Firewall Rule as suggested by Sophos as the "alternative" to HTTP/S bookmarks but is far from intuitive or easy to use for the end user. To be as secure as a Clientless VPN connection we are ending up having to set the allowed network to the range served by the SSLVPN server and install the SSLVPN client on end user's machines. This way they can only access the website if they have an account and are allowed SSLVPN access. This is a far cry from the simplicity of a bookmark in a user portal that at most requires one login. In summary, why is it that an OLD Cisco ASA is capable of doing something so simple and the "latest and greatest" from Sophos can't accomplish such a mundane function?