Regex

OK, I've been able to string match somewhat using the following:

if { ([HTTP::host] eq "subdomain.ourcompany.com") and ([string match {/webext/[0-999]*} [HTTP::uri]]) } {

when HTTP_REQUEST {
   Lowercase the URI for string comparison purposes (.aspx implies case-insensitive URIs)
  set uri [string tolower [HTTP::uri]]

   Only process URIs of the format /webext/xxxxx.aspx?status=error
  if { ($uri starts_with "/webext/") && ($uri ends_with ".aspx?status=error") } {

     Set the start index to the first char after "/webext/" in the URI
    set idxStart 8

     Set the end index to the dot in ".aspx".
    set idxEnd [string first ".aspx" $uri]

    if { -1 != $idxEnd } {
       decrement the end index to the last character in the id
      incr idxEnd -1;
      
       extract the id from the uri from the uri
      set id [string range $uri $idxStart $idxEnd]
      
       Issue the redirect
      HTTP::redirect "http://[HTTP::host]/post/post.ashx?id=${id}&status=error"
    }
  }
}

One other question - I've been told that these numbers will increment fairly quickly (the app is very buggy) and they've requested that I up the number quite a bit.

Let's say I want to use a number such as [0-99999999] - would I simply change your code to reflect that many characters?

when HTTP_REQUEST {
    Check if URI starts with /webext and there is a query string parameter named status set to "error"
   if {[string tolower [HTTP::uri]] starts_with "/webext" and [URI::query "?&[HTTP::query] &status] eq "error"}{
       Parse 000file.ext from /path/to/000file.ext and save the leading digits to the $id variable
       where 000 is one or more digits and file.ext is any string
      scan [URI::basename [HTTP::uri]] {%[0-9]%s} id rest
      if {$id ne ""}{
         log local0. "Scanned $id from $uri"
         HTTP::redirect "http://[HTTP::host]/post/post.ashx?id=${id}&status=error"
      }
   }
}

Turns out that rather than capturing ?status=error and passing it along, this needs to take whatever is after .aspx and append it, no matter what it is.

For example, they want the following examples to be able to work:

from:

http://server/webex/(.*).aspx?(.*)

to:

http://server/post/post.ashx?id=$1&$2

more examples:

http://server/webex/10.aspx?status=Good -> http://server/post/post.ashx?id=10&status=good

http://server/webex/10.aspx -> http://server/post/post.ashx?id=10

http://server/webex/234234.aspx?* -> http://server/post/post.ashx?id=234234&*

Does this iRule need to be completely re-worked all over again?

I was thinking of doing something like this:

HTTP::redirect "/post/post.ashx?id=${id}&[HTTP::query]"

rather than

HTTP::redirect "/post/post.ashx?id=${id}&status=error"

Thanks for any help, I'm trying to work on it on my own as well.

when HTTP_REQUEST {

    Check if URI starts with /webex/
   if {[string tolower [HTTP::uri]] starts_with "/webex/"}{

       Parse 000file.ext from /path/to/000file.ext and save the leading digits to the $id variable
       where 000 is one or more digits and file.ext is any string
      scan [URI::basename [HTTP::uri]] {%[0-9]%s} id rest
      if {$id ne ""}{
         log local0. "Scanned $id from $uri"
         HTTP::redirect "http://[HTTP::host]/post/post.ashx?id=${id}&[HTTP::query]"
      }
   }
}