Is there a way to allow only one directory and block anything else? For example, I want to allow x.x.x.x which will be automatically redirected to x.x.x.x/index.php which I want to allow but block anything besides this index.php
Hi Good question, I have had a quick look this morning at this, the issue is that the top level has to be permitted or the initial connection will, of course, be blocked, this means that you would have to create two custom categories one to allow the traffic and one to block all other traffic, this would need a full site map to be loaded into the Palo though as , for instance, a wordpress site would have artifacts required for correct rendering in sub-directories like wp-content for example, I did have mixed success with this, I then tried adding the category as a destination for an Allow rule and a Block rule respectively, this did not work, there was simply not enough control. You should be able to achieve this with the two custom category method but as I say they would have to be very comprehensive. As a note I was testing using standard navigation and not against a redirect however the request still comes from the client in both cases. Hope this helps a little!
Is there a way to allow only one directory and block anything else? For example, I want to allow x.x.x.x which will be automatically redirected to x.x.x.x/index.php which I want to allow but block anything besides this index.php
Hi
Good question, I have had a quick look this morning at this, the issue is that the top level has to be permitted or the initial connection will, of course, be blocked, this means that you would have to create two custom categories one to allow the traffic and one to block all other traffic, this would need a full site map to be loaded into the Palo though as , for instance, a wordpress site would have artifacts required for correct rendering in sub-directories like wp-content for example, I did have mixed success with this, I then tried adding the category as a destination for an Allow rule and a Block rule respectively, this did not work, there was simply not enough control.
You should be able to achieve this with the two custom category method but as I say they would have to be very comprehensive.
As a note I was testing using standard navigation and not against a redirect however the request still comes from the client in both cases.
Hope this helps a little!