SummaryUsing a specific HTTPS signature is for an application such as "abc.com/access" does not work due to encryption
OverviewWhen creating an HTTPS custom application for something like https://abc.com/access, it can be noticed that it does not work.
The reason for this is that Exinda will be able to see the server which is abc.com, however, once the session initiates and the file "access" is requested, this is encrypted in the session that was created. This is because it is not possible to have visibility into an encrypted communication without certificates. While the Exinda supplies this type of access for things like SSL Edge Cache, it does not deep dive into all possible conversations to gather this data.
So in terms of the HTTPS, application definitions done on Configuration > Objects > Applications will be limited to just the paramaters that are seen - things such as the common name of the certificate.
Eg. ssl-->common_name -->abc.com
However, if looking at the HTTP version of that, that is; http://abc.com/access, an application can be created using advanced options as the traffic is not encrypted:
Layer 7 signature http --> advanced --> common_name =% "abc.comt" and file %= "access"