madeye_80512
Dec 28, 2011Nimbostratus
Proper use of http redirect codes for temporary redirects?
Hi,
I'm pretty puzzled by the question on how to correclty(*) redirect on a LTM in case of a temporary disruption of service. In case of planned works as well as in case of something seriously wrong we intend to throw the users off onto another URL, i.e. they'd normally access
https://shop.xyz.com/
and we'd temporarily redirect them to another site
https://www.xyz.com/whatever/shopisdown.html
(*)trying to define "correctly": with the least evil effects (caching!) on popular and not so popular browsers or proxys.
The "fallback host" functionality in the http profile uses a 302 redirect when no poolmembers are available, but at least parts of the Internet state that 302 shouldn't be used because it is implemented strangely and was widely abused for somethings.
Triggering http::redirect from an irule throws a 301 which isn't good for the case(caching!).
This would leave a 307. This one is even dubbed "temporary redirect". We didn't try up to now and I'm somewhat scared because I don't feel that it is widely used and well understood.
Anyone with an opinion there?
Best regards
Me.