Forum Discussion

Brian_Kenworthy's avatar
Brian_Kenworthy
Icon for Nimbostratus rankNimbostratus
Feb 10, 2011

HTTP>HTTPS Redirect to different domain

Hi all, this should be pretty simple....hopefully.

 

 

I have a simple HTTP>HTTPS redirect in place for a domain --> HTTP::redirect "https://[HTTP::host][HTTP::uri]"

 

 

We have several subdomains (~15) xxx.domainA.com, yyy.domainA.com, etc. What we would like to do now is redirect those same sub domains to a new domain:

 

 

http://xxx.domainA.com to https://xxx.domainB.com

 

http://yyy.domainA.com to https://yyy.domainB.com

 

http://zzz.domainA.com to https://zzz.domainB.com

 

 

Is there any easier way to do this besides using a switch command for ever sub domain? I.E.

 

 

when HTTP_REQUEST {

 

switch [HTTP::host] {

 

xxx.domainA.com {

 

HTTP::redirect "https://xxx.domainB.com"

 

}

 

yyy.domainA.com {

 

HTTP::redirect "https://yyy.domainB.com"

 

}

 

etc...

 

 

Thanks in advance for the help!
application delivery
dev
devops
iRules
  • Chris_Miller's avatar
    Chris_Miller
    Icon for Altostratus rankAltostratus
    Feb 10, 2011
    I'd create a data group containing all the domains, check for a match, and if a match exists, use string to insert the value. Otherwise, you could use class search - value if you're on a newer version of code. What version are you on?
  • Brian_Kenworthy's avatar
    Brian_Kenworthy
    Icon for Nimbostratus rankNimbostratus
    Feb 10, 2011
    Thanks for the response Chris, I am running 10.2.0 HF2.

     

     

    Could you provide an example of the class search as it relates to what I am trying to do? I am not familiar with that functionality. Thanks!!
  • Chris_Miller's avatar
    Chris_Miller
    Icon for Altostratus rankAltostratus
    Feb 10, 2011
    Sure.

    You'd have a string type data group called something like "domainredirects." In that group, you'd have a string like "xxx.domaina.com" with a value like "xxx.domainb.com." Then, your rule would look something like this: 

    
when HTTP_REQUEST {
   if {  [class match [HTTP::host] eq domainredirects] } {
         HTTP::redirect "https://[class search - value  domainredirects eq [HTTP::host]]" }
}

    Otherwise, if your scheme is as simple as xxx.domaina.com > xxx.domainb.com, then a string command would be more efficient. All depends on how many characters you're changing I suppose.
  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Feb 10, 2011
    Nice suggestion Chris. You could save the second lookup by returning the name and value in the first lookup. Here's an untested example: 

    
when HTTP_REQUEST {
   set lookup [class search -element domainredirects equals [string tolower [HTTP::host]]]
   if {  [llength $lookup] == 2 } {
         HTTP::redirect "https://[lindex $lookup 2][HTTP::uri]"
   }
}

    Aaron
  • Colin_Walker_12's avatar
    Colin_Walker_12
    Historic F5 Account
    Feb 10, 2011
    @Aaron - Is there a reason for returning the element rather than the value in the search? You could save the lindex lookup if you returned the value directly. A bit nit-picky I suppose but I'm more curious if there's some reason you're doing it that I'm not seeing rather than trying to nit pick optimizations. ;)

     

     

    Colin
  • Brian_Kenworthy's avatar
    Brian_Kenworthy
    Icon for Nimbostratus rankNimbostratus
    Feb 10, 2011
    Thanks guys, I implemented Chris' solution and it worked like a charm, but when I tired Aaron's it did not work for some reason :(

     

     

  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Feb 10, 2011
    I like nit-picking to get the most efficient solution :). I was being a dolt and thinking of another recent conversation where we needed the matched name and value for later logic. In this case, you just need the matched value, so something like this should work: 

    
when HTTP_REQUEST {
   set host [class search -value domainredirects equals [string tolower [HTTP::host]]]
   if { $host ne "" } {
         HTTP::redirect "https://$host[HTTP::uri]"
   }
}

    Aaron
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Feb 10, 2011
    if you always know that you want to move domainA.com to domainB.com, you could do something more generic like this

    when HTTP_REQUEST {
  if { [HTTP::host] ends_with "domainA.com" } {
    HTTP::redirect "https://[getfield [HTTP::host] "." 1].domainB.com[HTTP::uri]"
  }
}

    That would redirect all requests to XXX.domainA.com to XXX.domainB.com retaining the URIs.

    Of course, if you have more domains to match on, then the class lookup will likely be a better solution.

    -Joe

  • yihwen_100254's avatar
    yihwen_100254
    Icon for Nimbostratus rankNimbostratus
    Jul 30, 2012
    Posted By Joe on 02/10/2011 01:44 PM

    if you always know that you want to move domainA.com to domainB.com, you could do something more generic like this

    when HTTP_REQUEST {
  if { [HTTP::host] ends_with "domainA.com" } {
    HTTP::redirect "https://[getfield [HTTP::host] "." 1].domainB.com[HTTP::uri]"
  }
}

    That would redirect all requests to XXX.domainA.com to XXX.domainB.com retaining the URIs.

    Of course, if you have more domains to match on, then the class lookup will likely be a better solution.

    -Joe

    Hi Joe

    Your suggestion looks good. Does your iRule works the same if we are redirecting from .com to say .com.sg?