For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

dubdub's avatar
dubdub
Icon for Nimbostratus rankNimbostratus
Nov 06, 2012

A strange case for catching an exception

Environment: 11.1.0 HF2 custom EHF build I have an iRule associated with a virtual server that's protected by an APM policy. This VS usually has north of 12,000 concurrent users, and is extremely...
application delivery
dev
devops
iRules
dubdub's avatar
dubdub
Icon for Nimbostratus rankNimbostratus
Jan 31, 2013
Just to close this thread out... suffice it to say that the minnow didn't catch anything. The errors have disappeared over the past six weeks and I haven't seen them for a while.

 

 

Result of the support case: since Apple isn't adhering to the specification in this situation, no changes to the HTTP::username function will be made. I will just need to add a catch around the function invocation to make sure my rule flows the way I want it to, even when an invalid base64-encoded string is sent through.

 

 

Thanks,

 

Jen