The Client and his citrix support (3rd party) explained that this config would ensure that only these URLs and file-endings would be allowed.
In our perception the Regex would obsolete the defined URLs since the Regex basically allwos any URL with the defined file-endings and a correct entry would need to look like:
If someone could confirm if the regex in the client's config obsoletes the other URLs (if the file-endings match) or confirm the clients config as correct would be much appreciated.
Question
Dominik Altermatt
We came across following configuration for a Start URL Relaxation Rule Set on a client's environment:
Entries:
1. https;//example.com
2. https://uat.example.com
3. ^[^?]+[.](html|js|jpg|png|css|pdf)$
4. https://demo.example.com
The Client and his citrix support (3rd party) explained that this config would ensure that only these URLs and file-endings would be allowed.
In our perception the Regex would obsolete the defined URLs since the Regex basically allwos any URL with the defined file-endings and a correct entry would need to look like:
^http://www[.]example[.]com/([0-9A-Za-z][0-9A-Za-z_-]*/)*[0-9A-Za-z][0-9A-Za-z_.-]*[.](asp|htp|php|s?html?)$ (as suggested be the citrix documentation under https://docs.citrix.com/en-us/netscaler/12/application-firewall/url-protections/starturl-check.html)
If someone could confirm if the regex in the client's config obsoletes the other URLs (if the file-endings match) or confirm the clients config as correct would be much appreciated.
Thanks
Link to comment
1 answer to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now