IRules mobile redirects help

Hi Ruchir,

 

 

Can you provide a few more examples of the URIs you want to redirect to the mobile site?

 

 

If the digits are present are they always in the third subdirectory of the path? Is it always a format like // // /letters/ /letters/? Or are there other formats?

 

 

Aaron

there can be many format, what we need to capture is digits from last and break point is either - or /

 

 

so if URI end is /234567/ - then ID = 234567

 

if URI last is /ar1-br2-cr3-3456/ then ID=3456

 

 

So it's always the last subdirectory that you want to parse? And are the digits always on their own // or // or following a hyphen like this /AAA-AAA-AAA-/ or /AAA-AAA-AAA-/?

If so you could try something like this example. Note that I haven't fully tested it. So if you see any issues can you reply back with the debug from /var/log/ltm?

when HTTP_REQUEST {

 Get the index of the last URI directory
set depth [URI::path [HTTP::uri] depth]

 Parse the last directory in the path
set last_dir [URI::path [HTTP::uri] $depth $depth]

 Parse everything after the last hyphen in the last directory
set digits [string trimleft [string range $last_dir [expr {[string last - $last_dir]}] end-1] -/]

log local0. "URI=[HTTP::uri], \$depth=$depth, \$last_dir=$last_dir, \$digits=$digits"

 Check if we parsed 4 or 6 digits
switch $digits {
[0-9][0-9][0-9][0-9] -
[0-9][0-9][0-9][0-9][0-9][0-9] {
 Found 4 or 6 digits, send a redirect
HTTP::redirect "http://m.site.com/test/?gid=$digits"
}
}
}

It would be more efficient if you could only perform this URI parsing for specific requests that might have the GID in the path. Do the requests always start with a standard path? Or is there another way that you could limit when you check for the 4 or 6 digits?

Aaron