ASM with Invalid File Types and poor web coding

Question

Hi all,&nbsp;
We are controlling allowed file types with an ASM policy, but found some poor web coding is leading the ASM to identify a particular URL as having a weird file type.&nbsp;
The end of a particular URL has "NFL0x20Season0x20No.of0x20Wins", and ASM picks this file type up as " of0x20Wins". There's no real chance of us getting the app developer to modify this behaviour, and I'm struggling to think of a way to configure the policy around it other than turning off that blocking option in ASM.&nbsp;
Anyone with some smart ideas to get around it?&nbsp;

iheartf5_45022 · Answer

Can you bypass ASM processing for the path using a local traffic policy? http://support.f5.com/kb/en-us/products/big-ip_asm/manuals/product/asm-implementations-11-4-0/20.html&nbsp;

milk_man · Answer

Could do that, or use an iRule with ASM::disable. Prefer not to, and wanted to see if there was any clever way other than not putting that traffic through ASM or having to disable Illegal File Type in the policy.

nathe · Answer

Is the uri repeatable or matching a pattern? Could you direct that traffic to a seperate asm policy with all file types allowed? That way u still get negative policy enforcement.&nbsp;
N&nbsp;

Forum Discussion

ASM with Invalid File Types and poor web coding

3 Replies

Recent Discussions

Geo Fence in ASM through irule for URI

Client certificate Authentication - open multiple tabs

google autenticator broken barcode

Chrome V 124+ on MacOS - Virtual Server Access Issue

vulnerabilities (CVE-2020-36363), CVE-2016-0736,CVE-2019-6593-FOR VERSION BIGIP LTM-16.1.4

Related Content

Application Programming Interface (API) Authentication types simplified

iRules Editor with Visual Studio Code

Security as Code eBook from NGINX

Access Logs - Invalid Tenant

Live Coding with iRules - Heatmaps!