Terence
My feedback
-
49 votesTerence
supported this idea
·
-
6 votes
An error occurred while saving the comment Terence
supported this idea
·
-
92 votes
An error occurred while saving the comment Terence
commented
This is also causing us issues with PCI scans for us. Not having fixed this for almost a year is shameful.
Terence
supported this idea
·
-
5 votesTerence
supported this idea
·
-
471 votesTerence
supported this idea
·
An error occurred while saving the comment Terence
commented
This is a basic requirement for a modern web applications, WebSockets have been around for years and years now. Heck, this "feature" request has been open for 2 years.
-
3 votesTerence
shared this idea
·
-
64 votesTerence
supported this idea
·
An error occurred while saving the comment Terence
commented
This just came up in a PCI scan for us as well, very disappointing to see it's been a request since March with no response.
Anyway, for anybody else who happens across this, on 9.3 we just added the "TraceEnable off" directive to configuration in /var/storage/chroot-reverseproxy/usr/apache/conf/httpd.conf and toggled the proxy service on and off in the UI. Seems to work fine.
Without this feature, each real webserver is a single point of failure. Most service failures aren't so obvious that they just stop responding entirely over the network - which means most service failures are not detected by the UTM.