Stripping part of URI and integrating with iRule

[HTTP::uri] is a cached item. Even though you've changed it with your string map statement, calling it from the redirect statement won't work because it's value is going to contain /directory1/directory2/.

 

 

Using HTTP::uri rewrites the URI between LTM and the pool member. Is that what you're trying to do or are you simply trying to send the user a redirect?

[HTTP::uri] is a cached item. Even though you've changed it with your string map statement, calling it from the redirect statement won't work because it's value is going to contain /directory1/directory2/.

 

 

Using HTTP::uri rewrites the URI between LTM and the pool member. Is that what you're trying to do or are you simply trying to send the user a redirect?

Yes, I am trying to rewrite from http://oursite.org/directory1/directory2/somepage.aspx to http://oursite.org/somepage.aspx

 

 

For some reason there are URL's that are actually http://oursite.org/directory1/directory2/ and still need to go somewhere....

 

 

Should I be using HTTP::path? I've tried that also with no luck. Not sure what I am missing.

Well, there's no need to use string map, I just realized that's not what I want as the URI needs to be rewritten

From:

http://oursite.org/directory1/directory2/somepage.aspx

to

http://oursite.org/somepage.aspx

I suppose HTTP::path would work too, however I haven't had luck with this iRule, still results in a strange loop:

when HTTP_REQUEST {

if { [HTTP::path] starts_with "/directory1/directory2" } {

HTTP::redirect "http://oursite.org[HTTP::uri]"

log local0. "/directory1/directory2 found, redirected"

} else {

HTTP::redirect "http://oursite.org[HTTP::uri]"

log local0. "go to homepage"

}

}

You're not "rewriting" the URI here. You're redirecting the user to a different one. For your else condition, are you just trying to direct them to their URI but without www in front of the host name? Or are you trying to redirect them to oursite.org/

With the rule above, [HTTP::uri] might contain /directory1/directory2. If it does, your first redirect is to send them to oursite.org/directory1/directory2. Naturally, that's going to be a loop. In the case of your else statement, the same logic applies.

Give this a shot

when HTTP_REQUEST {
  if { [HTTP::uri] starts_with "/directory1/directory2" } {
        HTTP::redirect "http://oursite.org[string range [HTTP::uri] 21 end ]" 
        log local0. "/directory1/directory2 found, redirected"
} else {
        HTTP::redirect "http://oursite.org[HTTP::uri]"
    log local0. "go to homepage"
  }
}

Hmm....doesn't seem to work, results in a redirect loop as well.

 

 

From logs:

 

 

 

Rule test HTTP_REQUEST: /directory1/directory2 found, redirected

 

 

 

And below that:

 

 

 

Rule test HTTP_REQUEST: go to homepage

 

 

 

what's the reason for the [string range [HTTP::uri] 21 end ]?

 

 

 

Also - as far as the else statement, if the user requests /directory1/directory2/somepage.aspx, the somepage.aspx needs to be kept, which I see the HTTP::uri will do for me.

 

 

 

Thanks for your help so far.

 

The string range statement grabs the range of characters from the 21st character to the last of the URI. So, it basically ignores the /directory1/directory2/ part and grabs everything after.

We should be able to get rid of the else statement. In the case where /directory1/directory2 doesn't exist, do you still want to get rid of the "www" if the user requested it?

This should cover the first part.

when HTTP_REQUEST {
  if { [HTTP::uri] starts_with "/directory1/directory2" } {
        HTTP::redirect "http://oursite.org[string range [HTTP::uri] 22 end ]" 
        log local0. "/directory1/directory2 found, redirected"
   } 
}

It also appears as if the bigip is trying to send my browser to oursite.org2 - it's placing the number 2 at the end of the url. Strange?

Heya - it worked!

 

 

I suppose I should have told you that I was masking /directory1/directory2, its actually not 22 chars, but 10 as we're using a 4 letter path

 

 

 

/aaaa/bbbb

 

 

 

so sorry - that's why I was wondering what the number was for.

 

 

 

Thanks for your help, once again very much appreciated!

 

My pleasure...also, I forgot a "/" so that's why the number 2 was getting placed onto your site name.

Give this a shot. We'll tweak the number of characters for string range to make it work.

when HTTP_REQUEST {
  if { [HTTP::uri] starts_with "/directory1/directory2" } {
        HTTP::redirect "http://oursite.org/[string range [HTTP::uri] 11 end ]" 
        log local0. "/directory1/directory2 found, redirected"
   } 
}