iRule for selecting ASM policy

Perhaps you can go down the VIP targeting VIP path.

 

First VIP has the iRule that determines the charset in HTTP_REQUEST, then send to a second virtual with the virtual iRule command which has the appropriate ASM policy attached.

 

Dear,

 

Thanks for your response.

 

The issue with VIP targeting VIP is... When a user logged in on a windows 1252 , VIP will target it to the windows 1252 security enabled VIP... After that, if the user changes to Windows 1256 encoded page.. it will not work..

 

We have thought of this approach. However, in our scenario.. it will not work..

 

Any other suggestions please..

 

how is the charset determined? Or rather, how do you distinguish on the traffic BIG-IP receives?

Shiraz. Is the charset based on uri possibly? A local traffic policy rule could forward particular URIs to one ASM policy and others to another... each using a different charset.

 

Just a thought.

 

another option is an ltm policy. I'm guessing here on how you determine (going with the Accept-Charset header, but you could also match on other headers on request or response):

ltm policy cpm.charsets {
    controls { asm }
    requires { http }
    rules {
        default {
            actions {
                0 {
                    asm
                    enable
                    policy /Common/asm_default_policy
                }
            }
            ordinal 3
        }
        win1252 {
            actions {
                0 {
                    asm
                    enable
                    policy /Common/asm_win1252_policy
                }
            }
            conditions {
                0 {
                    http-header
                    name Accept-Charset
                    values { Windows-1252 }
                }
            }
            ordinal 1
        }
        win1256 {
            actions {
                0 {
                    asm
                    enable
                    policy /Common/asm_win1256_policy
                }
            }
            conditions {
                0 {
                    http-header
                    name Accept-Charset
                    values { Windows-1256 }
                }
            }
            ordinal 2
        }
    }
    strategy first-match
}