Forum Discussion
How could I exclude Vulnerability scanners from Session Tracking?
- Jan 10, 2017
Is it bad form to answer my own question?
Anyhow, using logging I discovered that the violation name wasn't matching correctly. Here is a rule that I've now deployed and tested.
when ASM_REQUEST_DONE { if {([ASM::violation names] contains "SESSION_AWARENESS" && [ASM::violation count] < 2 && [IP::addr [IP::client_addr] equals n.n.n.n/m])} { ASM::unblock } }
F5 will not add last-modified headers unless you have additional profiles attached. You will need to check if the 304 message is actually being sent to the client. Use tcpdump and wireshark to confirm this.
As per my exp, It is by design the VLAN name cannot rename once it is created, all other parameters and options of the VLAN can be changed. The name is used as a fixed reference point for the VLAN allowing it to be referenced, thus changing the name would lose the reference to this specific VLAN. Only option to modify vlan name in config file & reload it. Or as you mentioned, we have to delete and config again .
i am not tried or done that in device.
The recommended way is to delete the VLAN and re-create it again.
But You could go into the configuration files and change the name and reload the configuration from the files. But then you need to edit the name on all places where it is used. You can try if needed. but always best and better way is deleting the VLAN and re-create it again.
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