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

schusb's avatar
schusb
Icon for Nimbostratus rankNimbostratus
Dec 18, 2018

<http_request> - ERR_NOT_SUPPORTED (line 2) invoked from within "HTTP::query"</http_request>

We've running an iRule on v13.1.0.6 which works fine. After upgrading to v14.1.0 the same iRule causes an error: err tmm[11570]: 01220001:3: TCL error: /Common/test_ir_asm_error-page - ERR_NOT_SU...
ASM Advanced WAF
iRules
security
Stanislas_Piro2's avatar
Stanislas_Piro2
Icon for Cumulonimbus rankCumulonimbus
Dec 27, 2018

You may not evaluate HTTP request after you execute a HTTP::respond or HTTP::redirect... F5 only enforced this in new versions.

 

In version 14.0, F5 introduced a new command to prevent this issue : HTTP::has_responded

 

try this code to leave the irule if another one made this one invalid.

 

when HTTP_REQUEST {
  if {[HTTP::has_responded]} {return}
  set mainPath "show-error-page"
  set mainPathExists "FALSE"
 
  set httpQuery [HTTP::query]
  set httpUri [HTTP::uri]
  set httpUrlMin [call ir_asm_library::getMinimalizedUrl]
 
  if {$httpUri contains $mainPath}
  {
      set mainPathExists "TRUE"
      set iFileErrorPageName [URI::query [HTTP::uri] "page"]
  }
}

 

  • Nick_T1's avatar
    Nick_T1
    Icon for Nimbostratus rankNimbostratus
    May 22, 2019

    Using "event disable all" followed by "return" is no longer sufficient under v14.1? Only the `HTTP::has_responded` method?

     

    I was previously accomplishing this behavior by putting those two commands in any iRule where I sent a response, but maybe there is a separate issue (like I need to do a log before the redirect first?)

Related Content