Filtering URLs
-
Hello,
I have a firewall that is forwarding the incoming requests to a web server. The web server hosts 3 different websites. I'd like to create some rules so that Access List 1 (whitelisted) can access web site 1 and 2 and Access List 2 (whitelisted) can access web site 3. Is it possible?Thanks,
D. -
You can either tailor your port forwards to only allow specified IP addresses as Source, or you could do it via web server directives in the site's config file, or via .htaccess.
-
@kom said in Filtering URLs:
You can either tailor your port forwards to only allow specified IP addresses as Source, or you could do it via web server directives in the site's config file, or via .htaccess.
But can;t I create an alias for List 1 and an alias for website 1 and a rule to match them?
-
@19giugno said in Filtering URLs:
@kom said in Filtering URLs:
You can either tailor your port forwards to only allow specified IP addresses as Source, or you could do it via web server directives in the site's config file, or via .htaccess.
But can;t I create an alias for List 1 and an alias for website 1 and a rule to match them?
Only if website 1 has a different IP address from website 2. Firewalls work off of the IP addresses and port numbers in an IP header. They don't understand URL text. What would you put in the alias you create to differentiate between the two websites?
The web server software itself (Apache, nginx, etc.) is what would read the incoming HTTP headers text and then route the request to the proper website. That's what @KOM was referring to: setting up filtering on the web server itself because that's the point in the chain where the acutal URL is decoded.
-
@bmeeks said in Filtering URLs:
@19giugno said in Filtering URLs:
@kom said in Filtering URLs:
You can either tailor your port forwards to only allow specified IP addresses as Source, or you could do it via web server directives in the site's config file, or via .htaccess.
But can;t I create an alias for List 1 and an alias for website 1 and a rule to match them?
Only if website 1 has a different IP address from website 2. Firewalls work off of the IP addresses and port numbers in an IP header. They don't understand URL text. What would you put in the alias you create to differentiate between the two websites?
The web server software itself (Apache, nginx, etc.) is what would read the incoming HTTP headers text and then route the request to the proper website. That's what @KOM was referring to: setting up filtering on the web server itself because that's the point in the chain where the acutal URL is decoded.
Thanks!