Forum Discussion

sjw1875_136904's avatar
sjw1875_136904
Icon for Altostratus rankAltostratus
Apr 11, 2014

iRule syntax change in upgrade to 11.5.0

Hello all,

 

I have upgraded our LTM from 11.4.3 to 11.5.0 at request of F5 support to fix an unrelated issue we were having.

 

However, this seems to have broken one of the iRules we have in place that is used for the F5 to front http based servers as https using a very useful DevCentral post - https://devcentral.f5.com/wiki/iRules.HTTPS-offload-rewriting.ashx

 

Since the upgrade to 11.5.0 and with this iRule assigned to my virtual server the connection fails with the following logged in the Local Traffic log -

 

"Status Code 01220001 / TCL error: /Common/Rewrite-HTTP - Operation not supported (line 1) invoked from within "HTTP::is_redirect""

 

I have tried a bit of tweaking to get this working, predominately removing the HTTP::is_redirect references, but I cannot get the rule to behave as it did pre 11.5.0.

 

Does anyone have an idea as to how I can make this 11.5.0 compliant?

 

Many thanks,

 

SjW

 

11.5.0
application delivery
devops
https to http rewrite
irule
iRules
LTM
  • sjw1875_136904's avatar
    sjw1875_136904
    Apr 15, 2014

    Hello all,

     

    F5 have identified this as a bug to be addressed in the next 11.5.1 hotfix to be released, 'ID452387 "HTTP::header is redirect" fails to work correctly'

     

    For reference, the iRule will work if the 'HTTP::is_redirect' reference is removed - my issue was a bit more involved that simply this HTTPS to HTTP redirect not working.

     

    Thanks,

     

    Scott

     

  • Mark_van_D's avatar
    Mark_van_D
    Icon for Cirrostratus rankCirrostratus
    Jun 24, 2014

    Just reading through the 11.5.1 HF3 release notes this issue does not appear to be addressed. Does anyone know if this is still being addressed? I'd prefer not having to rework existing irules.

     

  • Kevin_Stewart's avatar
    Kevin_Stewart
    Icon for Employee rankEmployee
    May 20, 2014

    This is indeed an issue with 11.4. You can use something like the following as a workaround:

    when HTTP_RESPONSE {
    if { [HTTP::header exists Location] } {
         ...this is a redirect response ...

    }
}
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    May 20, 2014

    Can you give an example?

      if { [HTTP::status] == 301 or [HTTP::status] == 302 } {
      do something
  }
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    May 17, 2014

    Does anyone know if this has yet been fixed?

     

    i understand it could be included in the next roll up. anyway, isn't checking HTTP header status usable?

     

  • nitass_89166's avatar
    nitass_89166
    Icon for Noctilucent rankNoctilucent
    May 17, 2014

    Does anyone know if this has yet been fixed?

     

    i understand it could be included in the next roll up. anyway, isn't checking HTTP header status usable?

     

  • Jon_S's avatar
    Jon_S
    Icon for Nimbostratus rankNimbostratus
    May 16, 2014

    Does anyone know if this has yet been fixed? I think I might still be having issues trying to use HTTP::is_redirect in 11.5 HF2