A Web Application Engineer is reviewing log files and finds that a large number of bad HTTP requests are being sent to the web application servers.
What can the Citrix ADC Engineer to do prevent bad HTTP requests from getting to the web application?
A Web Application Engineer is reviewing log files and finds that a large number of bad HTTP requests are being sent to the web application servers.
What can the Citrix ADC Engineer to do prevent bad HTTP requests from getting to the web application?
Creating custom HTTP profiles and binding them to specific virtual servers or firewall policies, as suggested in options A and B, is useful in certain scenarios but may not be comprehensive enough to address all bad HTTP requests across multiple servers. Modifying the default HTTP profile and binding it globally, as described in option C, ensures that invalid HTTP requests are dropped at a broader, system-wide level. This approach provides a more holistic solution for managing bad HTTP requests across the entire server infrastructure.
Reference - https://www.carlstalhood.com/system-configuration-citrix-adc-13/#profiles
A or D should both work
https://support.citrix.com/article/CTX227979/faq-strict-http-validation-on-netscaler-application-delivery-controller-and-netscaler-gateway
I´m agree with bengie but the aswer D is more specific A is to global level
with it saying web application servers (i.e. plural), applying this at a global level may be the way to go.