The redirection is well working when using Fire Fox & Internet Explorer but not on Chrome

I encountered a similar problem with redirects not being compatible with Chrome in the past while I was still using the

HTTP::redirect

Problem with Chrome is their unique way of optimizing HTTP performance. I've found that any F5 iRule redirects will not work with newer versions of Chrome no more than once per TCP connection, because F5 thinks the redirection was already executed for the incoming connection.

Steps to reproduce:
1) Close any opened Chrome Windows, open a new Chrome Window
2) Go to a URL that should redirect you somewhere (should work as expected)
3) Without closing the opened Chrome Window, open a new tab
4) Go to the same URL as in step 2 that should redirect you somewhere (will not work anymore)
5) The redirect at step 2 will not work until the connection times out, or until user tries to open the page from a new Chrome Window

To mitigate the problem, I started including a "Connection=Close" header with all F5-initiated redirects. For that, you must use HTTP::respond function instead of HTTP::redirect. Therefore, instead of your function

HTTP::redirect "http://[HTTP::host]/share"

HTTP::respond 302 Location "http://[HTTP::host]/share" Connection Close