Please provide the option in the Reverse proxy to enable encodedslashes for a specific virtual webserver.
Because some web applications use for example %2F for a slash and the reverse proxy cannot translate this back to / because of allowencodedslashes is not enabled by default. So this results in a 404 error.
This is essential for Web Applications like SAP Fiori! I think we not the only company who have this issue.9 votes
I neead to pass websocket protocol with WAF rule. It is one of very important protocol needed wit WEB servers.29 votes
Many small installation could benefit from ability to publish User Portal using Business Rule instead of enabling it directly in Device Access section. The difference is that a single IP can be used to host both User Portal and custom Web applications such as Web mail, Web storage, Web cameras, etc.
Now, the only solution is to change User Portal listening port to something non-standard but this limits the ability to use it from some network environments where only standard WWW ports (80,443) are allowed.91 votes
DSCP is a new feature but can be only used on User/Network rule. I would like to see the DSCP even on BAR in order to better manage multiple ISP.
Cyberoam has this feature.
Other UTM/WAF vendors integrate virtual patching features on their product. A really brute force protection in missing on WAF too.
Please add it.33 votes
It would be very nice if Let's Encrypt certificates (letsencrypt.org) can be generated directly from the XG Gui. So that the "Let's Encrypt Client" is integrated in the XG. Would it be possible?
Best Regards528 votes
We’re considering this
Adding a Business application non-HTTP rule you should have the option to use "Objects > Hosts and Services > Services" objects as the Port Forwarding target.
This reduces the rules required and keeps it more unified..
At the moment you need to add multiple rules I.E. A hosted service uses a mixture of single ports, port ranges and both tcp/udp will require multiple rules to achieve something very simple.95 votes
This is currently being developed for inclusion in v17
At the moment there are different type of authentication missing even on UTM9 against ISA server 2006, such as:
1. Two-factor authentication using forms-based authentication and a client certificate.
2. Delegation of credentials by using NTLM or Kerberos authentication.
3. Kerberos constrained delegation.
4. Secure Sockets Layer (SSL) client certificate constraints
In this way, XG and UTM9 are the very alternative to ISA Server.130 votes
- Don't see your idea?