Forum Discussion

1 Reply

  • I think there's actually a few ways to do this:

    APM customization: if you look in the BIG-IP management GUI, under Access Policy - Customization, then switch to Advanced Customization, and then Advanced Edit Mode, you can then drill down into the css files used by APM. From the tree on the left, go to Customization Settings - Access Profiles - [your access profile] - Common. Take note of the contents of apm.css. While I think you could insert a new css file through the file system, I think it might be just as easy to edit this css file to include your device-dependent css content.

    iRule: with this method we're listening for the client's request for apm.css and simply replacing it with a file of our own. You'll import and create an iFile (or several iFiles) and then reference them in the code based on the client's User-Agent header:

     

    when CLIENT_ACCEPTED {
        ACCESS::restrict_irule_events disable
    }
    when HTTP_REQUEST {
        if { [HTTP::uri] equals "/public/include/css/apm.css" } {
            switch -glob [string tolower [HTTP::header User-Agent]] {
                "*mozilla1*" {
                    HTTP::respond 200 content [ifile get mozilla_css] "Content-Type" "text/css; charset=utf-8"
                }
            }
        }
    }
    

     

    Of course both options should be used with caution.