Blocking requests before reaching the WebServer on Liferay PaaS (Public Cluster)
Written By
Madhusudan Sharma
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- We have encountered requests from unauthenticated sources on the webserver. Can these requests be blocked before reaching the webserver?
Resolution
-
We've two options present to deal with unwanted requests at the web server level, one is enabling the ModSecurity and the other is Blocking IPs that are unauthenticed.
- However, in front of the web server, the component we have is the GKE Ingress (firewall/Load Balancer), which gives internet access to your environment’s services via proxied HTTP(S) connections using TLS (1.0 to 1.2) protocol and diffuse traffic along with reducing the risk of services being overloaded.
- This Google Kubernetes Engine (GKE) ingress relies on GCloud HTTPS Load Balancer with WAF capabilities enabled and has some default firewall rules that are common for all the infrastructure, and it is not possible to customize them as per the requirements.
- Hence, it would not be possible to block the unwanted requests on any other component before the web server.
Did this article resolve your issue ?