Using a specific HTTPS signature for an application, e.g., abc.com/access, does not work due to encryption issues. This article provides relevant information to keep in mind in this scenario.
When creating an HTTPS custom application, it does not work. The reason for this is that Exinda will be able to determine the server, which in the example provided earlier is abc.com. However, once the session initiates and the file 'access' is requested, it will be encrypted within the created session; this is because it is not possible to have visibility of an encrypted communication without the correct certificates. While the Exinda supports this type of access for applications like SSL Edge Cache, it does not take a deep dive into all possible connections to gather this data.
In terms of the HTTPS, application definitions created under Configuration > Objects > Applications will be limited to the parameters presented to the user, e.g., the common name of the certificate. Under SSL > common_name, you could define common_name as 'abc.com.'
However, if you look at the HTTP version of that, an application can be created using advanced options, since the traffic is not encrypted. Under Layer 7 Signature HTTP > Advanced > common_name, for example, you could define the common_name as below:
common_name =% "abc.comt" and file %= "access"