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

Michael_A__Fied's avatar
Michael_A__Fied
Icon for Nimbostratus rankNimbostratus
May 21, 2010

iRule using URI classes to restrict access

(version 9.4.7) I have been restricting access to certain pools via the following iRule statement: if { [matchclass [IP::client_addr] equals $::TrustedIPs] and [matchclass [HTTP::path] starts_wit...
application delivery
dev
devops
iRules
Michael_A__Fied's avatar
Michael_A__Fied
Icon for Nimbostratus rankNimbostratus
May 24, 2010
Posted By Michael Yates on 05/21/2010 03:04 PM

The [HTTP::path] starts at the first "/" so you will either have to account for it in your matchclass or add to your iRule to look for it and remove it. 

HTTP::uri [string map {"//" "/"} [HTTP::uri]]

Wiki Entry for [HTTP::path] - http://devcentral.f5.com/wiki/default.aspx/iRules/http__path.html

Awesome, thanks, I'll test that later.

Is there any major advantage to performing the string map replace on the HTTP::uri vs the HTTP:path? We use extensive URIs and probably don't need to evaluate all the params in them.