Forum Discussion
uni
Jan 07, 2014Altostratus
It looks to me like it is saying that the HTTP::header command is not allowed within the ASM_REQUEST_BLOCKING event. Kind of strange, given that the example on the ASM_REQUEST_BLOCKING page does just this.
Perhaps enclose some of the code in try/catch, and do some extra logging of the payload when it fails.
- uniJan 07, 2014AltostratusUnrelated, but you should use 'contains' not '==' to test for the violation, as [lindex $x 0] is a comma separated list of violations
- TortiJan 08, 2014AltostratusThe problem is, that I cannot reproduce the error. I did add some extra log and changed to 'contains'. The 'contains' is a little bit strange, because in the wiki is the violation filed described as String. And I did never see a comma seperated list in the log, here. But it really looks like the system has some trouble with the HTTP::header command within the ASM_REQUEST_BLOCKING event. I tried "if { [HTTP::header exists Content-Length] } {}" before removing the header, but then I SOMETIMES get the TCL error: Illegal argument. Can't execute in the current context. (line 1) invoked from within "HTTP::header exists Content-Length"