Redirect loops are caused when the client receives a status code that falls within the redirection class, such as a 301 or 302 and is being redirected to the same location that the original request was made for.
In the case that traffic is being SSL offloaded at the LoadMaster, the server will be receiving requests on HTTP. Any redirects that the server issues will be to HTTP. For example, if a client requests "domain.com/signin.html" on HTTPS to the LoadMaster. The LoadMaster makes the request over HTTP to the server. At this point, the server believes that the client is trying to "sign in" over port 80 and issues a redirect to HTTPS "domain.com/signin.html". The client then connects again to the LoadMaster over HTTPS and receives the same redirect, resulting in a redirect loop.
This behavior can sometimes be fixed by simply injecting a header from the LoadMaster indicating that traffic is being SSL offloaded. However, if the application does not support SSL offloading, then enable "re-encrypt", or simply do not terminate SSL traffic at the LoadMaster.
Another scenario is when using content rules. If a client requests "domain.com/", the LoadMaster can redirect clients to "domain.com/newpage".
If the real server is also redirecting clients who connect to "domain.com/newpage", back to "/", then this can cause a loop also. The solution is to first confirm how the traffic is being redirected and then keep the redirection either on the LoadMaster or the server, but not both.