A tested iRule or Local Traffic Policy for Advanced WAF: selective policy bypass, header handling, custom logging or request steering. Where appropriate we convert the iRule to a Local Traffic Policy, the modern, HTTP-specific way to do the same job.
The iRule is the older way to extend ASM behaviour. F5 Local Traffic Policies now cover the same HTTP-specific jobs, selective policy bypass, header handling, request steering and logging, more cleanly and efficiently, so where appropriate WAFY builds a Local Traffic Policy or converts an existing iRule to one. Where an iRule is genuinely required, we write that instead. This service includes both: Local Traffic Policy creation and adjustment, and iRules where they are the right tool. Either way it is tested against real requests in a safe context and shipped with a short note on what it does and where it is attached, so the next engineer is not left guessing.
Illustrative examples, not a fixed list. If your job is the same shape, it fits.
An existing iRule reviewed and, where the function allows, converted to a cleaner, more efficient HTTP Local Traffic Policy.
A trusted internal path exempted from a policy, delivered as a Local Traffic Policy where possible, without weakening protection for everyone else.
A case that a Local Traffic Policy cannot express, written as a tested iRule instead.
Enquire and WAFY will scope it, confirm a fixed price in writing, and schedule it into the next window.
