ASM- Null in multi-part parameter value- Clarification

Are you familiar enough with this application that you can identify the real parameter names and file type extensions? That would help a lot in resolving the parameter-based violations (your illustration indicates more violations, not all of which are related to parameters.) It can be tedious to add the parameters one by one. If you change the learning scheme of your policy to "Always" you will soon see a list of parameters detected in traffic. This can help isolate problems related to parameters (you have 370 suggestions related to illegal parameter length in your example) from file types that might share the same name. Another option is to modify the attributes of the wildcard parameter (indicated by an asterisk: *) to allow a greater byte length than is currently specified--but not so permissive that you create buffer overflow or other DoS scenarios.