For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

David_Bohls_209's avatar
David_Bohls_209
Icon for Nimbostratus rankNimbostratus
Mar 03, 2011

301 Redirect to different port (iRule "Rewrite Redirect"

I currently have an issue where a client of mine is producing (301 302 305 etc...) redirects for certain traffic arriving on http://www.url.com:8081. The current iRule was not set up by me, and I bel...
application delivery
dev
devops
iRules
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Mar 03, 2011
Hi David,

It doesn't make sense to replace any 30x redirect with a 301 as that tells the client and any intermediate web proxies to cache the response. As you said, you could try using the rewrite redirect option on the HTTP profile. Or you could adapt a or precise iRule: 


From: http://devcentral.f5.com/wiki/default.aspx/iRules/RewriteHTTPRedirectPort.html
when HTTP_RESPONSE {

    Check if server response is a redirect
   if { [HTTP::header is_redirect]} {

       Log original and updated values
      log local0. "Original Location header value: [HTTP::header value Location],\
         updated: [string map ":[TCP::remote_port]/ / http:// https://" [HTTP::header value Location]]"

       Do the update, replacing :8080/ with / (where 8080 is the pool member's port) and http:// with https://
      HTTP::header replace Location [string map ":[TCP::remote_port]/ / http:// https://" [HTTP::header value Location]]
   }
}

Aaron