For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

yvuppnuti_29397's avatar
yvuppnuti_29397
Icon for Nimbostratus rankNimbostratus
Oct 13, 2016

TCL error HTTP to HTTPs redirect

Hi when i see logs in LTM device

 

I am getting this error:

 

TCL error: /Common/http_to_https_redirect - Operation not supported. Multiple redirect/respond invocations not allowed (line 1) invoked from within "HTTP::redirect https://[getfield [HTTP::host] ":" 1][HTTP::uri]"

 

Please help me what is this error and which VIP is getting this error and the irule is

 

when HTTP_REQUEST { HTTP::redirect https://[getfield [HTTP::host] ":" 1][HTTP::uri] }

 

and i couldn't find any VIP details in TCL error from logs is there any way that i can find out the VIP.

 

Thanks

 

devops
iRules
LTM
security

2 Replies

  • Stefan_Klotz's avatar
    Stefan_Klotz
    Icon for Cumulonimbus rankCumulonimbus
    Oct 13, 2016

    Looks like you are using at least on VIP with this an another iRule, which also tries to perform any kind of redirect or respond command (which is normally the reason for this error message). If there are really no further details in the log which VIP is triggered here, logon to the CLI and open the bigip.conf file to search for it, assuming you are not working with partitions:

    pico /config/bigip.conf

    There you can search with Ctrl+w and enter "/Common/http_to_https_redirect", repeat Ctrl+w to search for more than one occurrence.

    Ciao Stefan 🙂

  • VernonWells's avatar
    VernonWells
    Icon for Employee rankEmployee
    Oct 13, 2016

    To expand a bit on that, normally this error occurs when an explicit redirect is attempted more than once on a single flow. This can occur when a redirect is attempted more than once in the same rule for a common code path, if you have more than one rule attempting a redirect applied to the same Virtual Server, or if you attempt a redirect both with a rule and with an HTTP Local Traffic Policy (or Traffic Class).