Forum Discussion
HTTP Profile
- May 09, 2021
Hello Sushant.
AWAF is able to protect web portal because it interprets and analyzes HTTP traffic searching for potential attacks. So, configuring a HTTP profile is mandatory. That means that you have to be able to interpret the whole set of OSI layers (from L4 to L7).
First question you have to ask you is:
Is my backend server (API server) using TLS?
If the answer is yes, you have to put a server SSL profile in your VS.
Second question is:
Do I want to use TLS in my front-side communication for the VS?
If the answer is yes, so I also need to put a client SSL profile in my VS.
Remember that without SSL profiles, F5 won't be able to decrypt that trafffic and without decrypting it there is no WAF protection possible.
Regards,
Dario.
Hello Dario,
Thank you replying back...
Yes I did get your point and in order to use TLS as per my understanding a domain name must be there with their associated DNS record. But in my particular case API has only IP associated (no domain) with it which communicates using a layer2 MPLS link that means there wont be any domain associated with it as there will direct communication using IP over MPLS.
The API is plainly working on HTTP as well so SSL profile is not required as well.
Is there any workaround for these kind of scenarios where I could be using all security profiles ?
thanks Dario !
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