BIG-IP : create data-group fails with format error
f5 BIG-IP LTM VE v11.4.0 on ESXi I am attempting to create a new data-group : Type = "(External File)" File Contents = "String" Key/Value Pair Separator = ":=" My external data-file 'test.txt' : "test-1" := "test-1", "test-2" := "test-2", What is strange is that I've previously successfully loaded data in exactly this format. However, now I receive this error : 0107169a:3: The data group external file (/config/filestore/.stage_d/107479_d/Common_d/data_group_d/:Common:test_57194_1) has an invalid format, line: 2. I've tried removing the final comma on line 2 : "test-1" := "test-1", "test-2" := "test-2" but receive the same error. With a single row : "test-1" := "test-1", the data loads with no error.546Views0likes3CommentsBlocking specific file names while allowing specific file type
Hi all, What would best way to allow file1.exe file2.exe to enter, but block ALL other *.exe files. Also while *.exe is allowed as a file type within ASM policy. I'm worried about order of operations. I'm working with 12.2 and I don't see ability to enter regex for file types. I was hoping I could do this like I would do regex within parameter type. Any suggestions? What if I I block *.exe as file type in ASM but then have file1.exe file2.exe as irule to allow it? What about creating a unique ASM signature? If anyone is doing this would appreciate some input. Looking for best approach.257Views0likes0CommentsDynamic URLs setting off illegal file type events. eg. https://site.com/email/jim@jim.com
Hi Guys, One of our applications dynamically passes text from an text box to the URL as the user types resulting in lots of illegal file type events. The text box allows users to enter an email address and as the user types, the app posts the data that is provided to check if the email is valid and if the email is already in use. I have tried to create a wildcard allows url eg. /api/email/* expecting that this path would then be excluded from the ASM policy rules however even with this exclusion in place the ilelgal file types rule is still triggered for every character typed. For the moment I have set a wildcard file type which will allow any file type to be requested which is not ideal however it provides usability. Any advice on rectifying this would be great. Thank you.235Views0likes1Comment