Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

Tyson_James's avatar
Tyson_James
Icon for Cirrus rankCirrus
Jul 18, 2024

Redirect iRule differences...

We have a situation where we need to redirect users from one domain to another and had been using Method 1 ( shown below ) of redirection via iRule.  It was recently brought to our attention by our w...
irule
LTM
redirect
Paulius's avatar
Paulius
Icon for MVP rankMVP
Jul 18, 2024

I wasn't aware of how this caused issues for SEO but the following article seems to explain it a bit.

https://www.incrementors.com/blog/why-302-redirect-can-hurt-your-website-and-seo-efforts/

Now from a technical standpoint, the biggest difference between "HTTP::redirect" and "HTTP::respond" is that redirect is always an HTTP 302 where as a respond allows you to respond with a specific HTTP status code, in this instance you are responding with a 301. If additional changes to the redirect are coming soon then you might opt for an "HTTP::redirect" and then when it's permanent you can configure "HTTP::respond 301". If you plan on making this switch you might consider using "HTTP::respond 302" and then changing it to "301" later so that the majority of the syntax remains the same.