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

f5noob29's avatar
f5noob29
Icon for Altocumulus rankAltocumulus
Jan 21, 2021

301 Redirect but Adding Original URL and Referrer

Old website will be decommissioned and we want users that would access the old site to be redirected but with the original URL be added and a referrer in the header. Can the original URL can be passe...
application delivery
BIG-IP
iRules
f5noob29's avatar
f5noob29
Icon for Altocumulus rankAltocumulus
Jan 27, 2021

Thanks Kees.

 

I got it to work but app owner says that they are seeing below,

 

Location: https://https://NEW-APP.com/redirect?url=http://old-app.com-help/URI/URI1/URI2/URI3

 

Instead of this,

 

Location: https://NEW-APP.com/redirect/?url=http%3A%2F%2Fold-app.com%2FURI%2FURI1%2FURI2%2FURI3

 

They also want to have a cache-control header

Cache-Control: no-cache, no-store, must-revalidate, max-age=0

 

Also the referrer does not seem to work as F5 doesn't include the referrer in the redirect URL.

 

TIA.

f5noob29's avatar
f5noob29
Icon for Altocumulus rankAltocumulus
Jan 27, 2021

Hi,

This is what i currently have but it does not seem to be working. I used the iRule that you suggested but ended up modifying it as it is not working according to their requirements and so that's the end result. 

when HTTP_REQUEST {
set uri [URI::encode [HTTP::uri]]
set host [URI::encode [HTTP::host]]
set referer [URI::encode [ HTTP::header Referer ]]
 
	if { [string tolower [HTTP::uri]] starts_with "/URI/"} {
	  HTTP::respond 301 Location "https://NEW-APP.com/redirect/?url=http://$(host)$(uri)__referrer=${referer}&[HTTP::query]" { HTTP::header replace "Cache-Control" "no-store, no-cache, must-revalidate, max-age=0" }
	}
}