Forum Discussion

Sam_Hall's avatar
Sam_Hall
Icon for Nimbostratus rankNimbostratus
Mar 24, 2016

HTTP Super SIDEBAND Requestor warnings on v11.6

BIG-IP 11.6.0 Build 6.119.442 Engineering Hotfix HF6 gives a bunch of warnings for this iRule...

 

/Common/HSSR:359: warning: [variable reference used where variable name expected][$opt]
/Common/HSSR:808: warning: ["\x" has no meaning.  Did you mean "\\x" or "x"?][{^HTTP/1[.][01]\x20([0-9]+)[^\r]*\r\n}]
/Common/HSSR:808: warning: ["\r" has no meaning.  Did you mean "\\r" or "r"?][{^HTTP/1[.][01]\x20([0-9]+)[^\r]*\r\n}]
/Common/HSSR:808: warning: ["\n" has no meaning.  Did you mean "\\n" or "n"?][{^HTTP/1[.][01]\x20([0-9]+)[^\r]*\r\n}]
/Common/HSSR:847: warning: ["\r" has no meaning.  Did you mean "\\r" or "r"?][{^(?:[\r\n])*([0-9A-Fa-f]+)[^\r]*\r\n}]
/Common/HSSR:847: warning: ["\n" has no meaning.  Did you mean "\\n" or "n"?][{^(?:[\r\n])*([0-9A-Fa-f]+)[^\r]*\r\n}]
/Common/HSSR:954: warning: ["\r" has no meaning.  Did you mean "\\r" or "r"?][{[\x20\t]*\r\n[\x20\t]+}]
/Common/HSSR:954: warning: ["\n" has no meaning.  Did you mean "\\n" or "n"?][{[\x20\t]*\r\n[\x20\t]+}]
/Common/HSSR:1010: warning: ["\y" has no meaning.  Did you mean "\\y" or "y"?][{(?i)\ySecure;?\y}]
/Common/HSSR:1010: warning: ["\y" has no meaning.  Did you mean "\\y" or "y"?][{(?i)\ySecure;?\y}]
/Common/HSSR:1076: warning: ["\y" has no meaning.  Did you mean "\\y" or "y"?][{(?i)\yclose\y}]
/Common/HSSR:1076: warning: ["\y" has no meaning.  Did you mean "\\y" or "y"?][{(?i)\yclose\y}]
/Common/HSSR:1098: warning: ["\x" has no meaning.  Did you mean "\\x" or "x"?][{(?i)Basic\x20}]
/Common/HSSR:1106: warning: ["\x" has no meaning.  Did you mean "\\x" or "x"?][{(?i)Basic\x20}]

 

2 Replies

  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus

    Have you just upgraded to HF6? Sounds like there is a bug in the upgrade process somewhere. I'd contact F5 TAC for this.

     

  • These particular warnings are bogus and do not indicate bugs in the HTTP Super Sideband Requestor. BIG-IP TMOS has an iRUles (TCL) code validator which looks for symptoms of coding errors sometimes made by less experienced iRules developers (or accidentally added as typing mistakes by more-experienced coders!). Some of the things the validator flags are legitimate constructs that just happen to resemble common errors, in particular, "indirection" in assignments, like:

     

    set a 0
    set indirect_reference "a"
    set $indirect_reference 1
    log local0.info "after assignment, a = ${a}"
    
    after assignment, a = 1
    

     

    Indirection looks like the common error of putting a $ in front of the name of the destination variable in a set command, but intentional indirection is not an error. The validator cannot tell the difference so it issues a warning every time.

    The warnings about \whatever are also bogus; the validator does not understand regular-expression syntax.