Forum Discussion
NimbostratusThe redirection is well working when using Fire Fox & Internet Explorer but not on Chrome
Hello All,
The redirection is well working when using Fire Fox & Internet Explorer. But when customer trying to reach the page on Chrome url is not redirected
URL-http://uat-alfresco-euro.kamlesh.com:2095/alfresco/faces redirects to http://uat-alfresco-euro.kamlesh.com:2095/share
Please help me . Thanks in advance.
Regards Kamlesh Y
10 Replies
Stanislas_Piro2Cumulonimbus
share your config if you want help... do you use an irule, a local traffic policy??? post here the configuration... (with anonymized IPs and hostnames...)
natheCirrocumulus
What happens if you enable the developer tools for Chrome, do you see anything in here to suggestion an issue?- kamlyada_209668Hello, VIP name -vs-alfresco Pool name -Alfresco Nodes attached to it- 10.155.53.201:2095 10.155.53.202:2095 Three Irule has been atttached to the VIP below is 1) sorry page if no server are available 2) insert in http header X-forwarder for client Ip address 3)The one for redirection mentioned below which we are facing issue only on chrome-- when HTTP_REQUEST { if {[string tolower [HTTP::uri]] starts_with "/alfresco/faces"}{ HTTP::redirect "http://[HTTP::host]/share" } } Above redirection is working well for IE and Mozilla but not for chrome. Kingly help and suggest Thanks in advance. Regards Kamlesh Y
Hannes_Rapp_162Nacreous
I encountered a similar problem with redirects not being compatible with Chrome in the past while I was still using the
function in my iRules. It might be related with your issue, but not sure.HTTP::redirectProblem 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 WindowTo 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
, give a try toHTTP::redirect "http://[HTTP::host]/share"
. Let's see if it will help you.HTTP::respond 302 Location "http://[HTTP::host]/share" Connection Close- Hannes_Rapp_162Forgot to add, since you have multiple iRules, you may also suffer from multiple HTTP response/redirect violation - check /var/log/ltm to confirm. After each use of HTTP redirect or response function, use the 'event disable' function to make sure other iRules will not override an action. You can check more about the multiple redirect/response invocation issue here: https://devcentral.f5.com/questions?pid=42824answer128487
- kamlyada_209668Thanks for your help and i will try the above I-rule and will let u know. Regards Kamlesh Y
- Hannes_Rapp
I encountered a similar problem with redirects not being compatible with Chrome in the past while I was still using the
function in my iRules. It might be related with your issue, but not sure.HTTP::redirectProblem 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 WindowTo 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
, give a try toHTTP::redirect "http://[HTTP::host]/share"
. Let's see if it will help you.HTTP::respond 302 Location "http://[HTTP::host]/share" Connection Close- Hannes_RappForgot to add, since you have multiple iRules, you may also suffer from multiple HTTP response/redirect violation - check /var/log/ltm to confirm. After each use of HTTP redirect or response function, use the 'event disable' function to make sure other iRules will not override an action. You can check more about the multiple redirect/response invocation issue here: https://devcentral.f5.com/questions?pid=42824answer128487
- kamlyada_209668Thanks for your help and i will try the above I-rule and will let u know. Regards Kamlesh Y
jsgibbs1Old post but was exactly what I needed! Thank you!!!!
