Rewriting only part of the URI

I think I've got it - I simply used a string map, and incorporated HTTP::redirect vs HTTP::path as to perform the rewrite / redirect.

 

 

when HTTP_REQUEST {

 

 

 

Check if path starts with /newsletters/Directory2

 

if {[HTTP::path] starts_with "/newsletters/Directory2"}{

 

 

Replace /newsletters/Directory2 with /newsletters/Directory3 in the path

 

HTTP::redirect [string map {/newsletters/Directory2 /newsletters/Directory3} [HTTP::path]]

 

}

 

}

 

 

 

 

 

So with something static like /newsletters/ beginning your URI, you could do a string range (in tlcsh):

set x "/newsletters/Directory2/something/else/entirely/file.txt"
puts "/newsletters/Directory3[string range $x [string first / $x 13] end]"

/newsletters/Directory3/something/else/entirely/file.txt

so in iRules, that would be

HTTP::uri "/newsletters/Directory3[string range $x [string first / $x 13] end]"

might need tweaking if not as static as you presented in the request, but gets you along the way...

For some reason, when I start adding on string tolower, I keep getting redirect loops. I want to be sure I catch any case in the browser and set it to lowercase - any idea what I may be missing here?

when HTTP_REQUEST { 
  
   Check if path starts with /newsletters/directory2 
    if { [string tolower [HTTP::path]] starts_with "/newsletters/directory2"}{ 
  
        Replace /newsletters/directory2 with /newsletters/directory3 in the path 
       HTTP::redirect [string map {/newsletters/directory2 /newsletters/directory3} [HTTP::path]] 
    }
 } 

OK - I think I got it again - unless someone sees a problem with this performance wise:

when HTTP_REQUEST { 
  
   Check if path starts with /newsletters/directory2 
    if { [string tolower [HTTP::path]] starts_with "/newsletters/directory2"}{ 
  
        Replace /newsletters/directory2 with /newsletters/directory3 in the path 
       HTTP::redirect [string map {/newsletters/directory2 /newsletters/directory3} [string tolower [HTTP::path]] ] 
    }
 }

Hi Joe,

 

 

Jason's example using string range is more exact and possibly slightly more efficient. But if the string map is working for you it should be fine.

 

 

Aaron

Hmm....will his example work if the length of the entire path varies? When I saw the [string first / $x 13], I was under the impression that it would only replace X number of characters...

 

 

Here's a few example paths:

 

 

http://ourdomain.com/newsletters/directory3/2011/04/20110420.aspx

 

 

and

 

 

http://ourdomain.com/newsletters/directory3/2011/04/20/asomewhat-long-pathforthe-file-tryingtoreach.aspx

 

 

As always, your help is greatly appreciated. The string map is working great for me so far, the F5's are still sleeping....

so what the string range is doing is taking all the content immediately after /newsletters/directory2. The string first is finding the appropriate start index for the string range by looking for the first "/" in HTTP::uri AFTER the first 13 characters. So this could be /newsletters/ or anything else that was 13 characters long. If it was going to be dynamic in length, then you would want to utilize URI::path and string length as part of the equation, then you wouldn't need to specify newsletter/directory2 at all. Fun stuff!

Nice! Thanks guys!