Wildcard URL with "dot" allowed confused with a file type

Question

Hello  evryone&nbsp;I configuered a wildcard URL (/x/y/*) in my ASM policy with the "." as an allowed meta character, but all the requests /x/y/1245.452 for example are blocked by violation illegal file type, does anyone know how to fix this issue ?&nbsp;Thanks in advance

andrew-f5 · Answer

There's really only two solutions:(1)  Accept the filetype and do nothing(2) create a wildcard file type which will accept all non-explicit filetypes including no_ext.&nbsp;    no_ext filetypes are those urls with no periods that works in conjunction with wildcards&nbsp;    Note that the burden of enforcement will shift to url matching.     &nbsp;    violation will not be a bad filetype, but rather an unknown url&nbsp;There is a feature request to prevent this behavior but it hasn't been added to any F5 software yet ID400017.&nbsp;

Forum Discussion

Tyler - May 2026 Featured Member

AppWorld Berlin 2026 – iRules Contest Winning Results

One Quick Step to Make your website AI-Agent/MCP Ready with an iRule

Recent Discussions

Procedure for migration LTM/GMT cluster form serie I to R

F5 VCMP guest shutdown and decommissioning

OpenID Connect as Client and Resource server

F5 BIGIP & XC certbot plugin

F5OS cloud-init on 21.1 does tenants come with DO and AS3 RPM installed?

Related Content

Cache Confusion

AS3 TLS_Client VS TLS_Server Schema confusion

Wildcard Parameter signature attack

Wildcard Certificate

iRule http host with wildcard domain