Forum Discussion
File upload and ASM
- Sep 07, 2023
Bypass for an ASM policy better be done just for the violation with an irule as I see it as to not stop the ASM checks for urls , headers etc. and this way you are making a smaller security hole 😗. This is a nice example:
https://clouddocs.f5.com/api/irules/ASM__unblock.html
Other option that can be tested is Request Body Handling, select Do Nothing. under the url:
https://my.f5.com/manage/s/article/K32081491
What was mentioned till now are all good solutions.
Hi marta_sl ,
beside Sebastiansierra comment which is exactly correct , I want to add something important , if you intent to set value more than 10 MB , it's crucial to monitor your memory before the change and after , this increasment in request buffer size will consume from memory and you can't measure this impact because it depends on the number of requests which are processed by ASM engine so if you have now a high utilization of system memory , it's recommended not to set higher values of request buffer size in asm variable attributes >>> also take in your consedration this value will applied in all ASM policies not only for the policy you are complaining from it.
> I would provide you another workaround if you have high memory utilization:
you can bypass the url that contains this large file/video form being processed by ASM , you can do this using LTM policies or irules.
you will the steps of by bypassing in this article : https://my.f5.com/manage/s/article/K22021244
Thanks Sebastiansierra for your detailed comment.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com