"Must be Unique" Error messag assigning iRule

Hello all,

 

 

Prior to this ASP.Net Vuln issue I had one iRule assigned to all my VIPs which was simply to reject Blank Headers, the code is below. Since then we added a simply redirect to our custom 404.aspx page when a response is 404 or 5*, the code is also below, I successfully assigned that rule to all VIPs. Finally today I created a new iRule that checks the query string and if there is a match it redirects to the new 404.aspx page, code is below. However this time when I attempt to assign I get an error message" "Must be Unique". I'm doing the assigning from the F5 iRule Editor, (ver-10.1.0). If I add the new iRule via the F5's GUI interface it adds with out issue. Through some troubleshooting I found that if I remove the ASP Vuln redirect rule I can add my new iRule without issue. I also looked into setting priorities for the Blank Header rule and my new iRule since both use HTTP_Request but that didn't seem to change anything.

 

 

I'm running version 10.2 on the BigIP. Anythoughts or suggestion on what I'm doing wrong or what I can do to make this work with out having to touch a 100 or so VIPs? I wouldn't even mind combining them all into one, but I'm not sure how to do that.

 

 

Name: QueryPram_Redirect

 

 when HTTP_REQUEST { 
   if {[HTTP::query] contains "aspxerrorpath="}{ 
      redirect to http://DomainName.com/404.aspx 
      }   
 }
 

 

 

Name: ASP_Vuln_Fix

 

when HTTP_RESPONSE { 
      if { ([HTTP::status] starts_with "404") || ([HTTP::status] starts_with "5")} { 
         redirect to "http://DomainName.com/404.aspx"
   }
 }

 

 

Name: BlockNoHeader

 

 
when HTTP_REQUEST { 
      if { [HTTP::host] equals "" }
          { reject 
   }
 }

 

 

Thanks,

 

Bob