Forum Discussion
GavinW_29074
Nimbostratus
NimbostratusCatch specific SSL errors/failures???
Hi there
One of the requirements that I've been given is to try and catch certain SSL errors and return a more friendly error page, rather than the browser default...
A couple of ...
GavinW_29074Nimbostratus
NimbostratusOk, results are in...
With the 'get ifile' command on each request:
show CatchSSLErrors
--------------------------------------------
Ltm::Rule Event: CatchSSLErrors:HTTP_REQUEST
--------------------------------------------
Priority 10
Executions
Total 200
Failures 0
Aborts 0
CPU Cycles on Executing
Average 664.4K
Maximum 1.6M
Minimum 0
-----------------------------------------
Ltm::Rule Event: CatchSSLErrors:RULE_INIT
-----------------------------------------
Priority 500
Executions
Total 1
Failures 0
Aborts 0
CPU Cycles on Executing
Average 0
Maximum 0
Minimum 0
With the 'get ifile' commands in the RULE_INIT block:
show CatchSSLErrors
--------------------------------------------
Ltm::Rule Event: CatchSSLErrors:HTTP_REQUEST
--------------------------------------------
Priority 10
Executions
Total 200
Failures 0
Aborts 0
CPU Cycles on Executing
Average 639.6K
Maximum 1.0M
Minimum 0
-----------------------------------------
Ltm::Rule Event: CatchSSLErrors:RULE_INIT
-----------------------------------------
Priority 500
Executions
Total 1
Failures 0
Aborts 0
CPU Cycles on Executing
Average 0
Maximum 0
Minimum 0
This was with a request size of 200 attempts...
So there's definitely a difference between the 2..
Is it likely to make a big difference? As I'm not that familiar with what's good and what's bad when it comes to iRules and timings...
Cheers
Gav