HTTP Proxy - Customizable Block Page Content Based on Error Type
Provide a mechanism whereby the block page that results from various operations is different and customizable based on the reason for the page being displayed (page not found, vs page blocked for cff vs page blocked for virus etc...). Ensures the end user is not confused by the page they are presented with, such as a DNS timeout looking like a content filter block page.
My users don't understand the "Reason" field, and I don't expect them to. But when a site doesn't exist, or it's malicious, they see the same "Blocked" site page, and they get angry. I'd like to be able to present a different customizable page for each category that would make it clear to them visually when a site is either blocked or a failure for some other reason. Rather than deal with calls to allow some hacked site, and having to explain to them why I can't allow it, a nice big red warning version would be good. A friendly blue version for when they have to request access, and maybe a green version that says when a site is unavailable because it doesn't exist.
Don't tell user that a URL is blocked when it doesn't exist (404 error)
Currently, when using the Proxy in "Standard" mode (browsers point at the Proxy) and the user enters a non-existant URL, the Proxy incorrectly reports
"The content is blocked due to the following condition:
" The URL you have requested is blocked by Surf Protection. If you think this is wrong, please contact your administrator. "
This confuses many users and causes unnecessary problems for admins.
The End-user GUI elements (E.g When a website is blocked, when your downloading a file, etc) could use with a refresh as in its current state its quite sore on the eyes. Some of my users even thought it was some kind of dubious site. Also the ability to customize the URL (http://passthrough.fw-notify.net) to something more friendly would be welcome as well.
I'm looking for a option to edit the Proxy / Alert Sites to use our corporate design with own messages and logos. BTW: Some Proxy Alerts are not editable. For example "Host nod found" or "Content not allowed"
actually it´s possible to customize status/error pages in the http-proxie by definining new messages and adding a company logo.
It would be interesting for some customers, if they were also able to change the design of this pages to make them fit their company design/corporate design.
Everyone likes to see in his browser a detailed description for blocked or inaddressable contents - OK.
The idea is to use the footbar or bubbles to display the complete information when the mouse hovers over. This would be very useful in cases where the required space for the notification is smaller then the available space in that site.
It would be very helpful for troubleshooting if the administrator can select which additional information will be shown on the error page of the http proxy. I suggest the following options: date, time, client ip, unique request id, cluster node id (if clustering is used).
Furthermore the reason for getting the error page (e.g. host not found, connection refused, connection to server timed out) should be highlighted red.
More times than not, the URL in the Block Page is so long that more than half the page runs off the side of the screen.
It would be nice if a little work was done to configure the table to fit the window and the cells to word-wrap.
Unfortunatly it is actually not possible to modify the proxy message for blocked file extensions.
We have customers all over gemany which customize their notifications, to tell the users clearly, why a website or a file download is blocked by astaros web security.
I was recommended to open a feature requests for the customization of the "blocked file extension message".
When your users use the http proxy then should receive all error messages in their native language.
The ideal would be to have the possibility of editing them from the webadmin and greater adaptation to our needs than it is today. We need more customization end-user-visible messages or strings used by the HTTP Proxy. In particular, the blocking of content. There are many reasons for ASG to display the standard "blocked" page and where the user gets no or only a confusing message. The funny thing is, that in some cases even the administrator can't tell what has happened.
This feature has been released as part of UTM 9.1. Enjoy!
Evan Hart commented
This same thing happens when URL's refer to bad/non-existent hosts or valid hosts/IP's but unresponsive servers.
+1 (if I had any more votes)
Rudolf Eksteen commented
Yes this would be a great future. Also the ability to display the category if being blocked for web filter. quicker to troubleshoot.
Finally! Thanks very much. This is a real annoying bug in Astaro ASG/Sophos UTM!
James White commented
Awesome, can you confirm that this will also work with the Web Application "reverse proxy"?
James White commented
Yes please. A custom 503 error page whilst updates on web servers are being done would be very very useful to me.
Bob Alfson commented
Angelo commented that V9.1 will have some sort of redirect capability. Perhaps this can be combined with those changes.
David B. commented
David B. commented
oh yes please, our users do not read very good English. it would be easier for them to have custom pages.
Marcos Machado commented
2 years and still nothing... :( About 50% of my support tickets can be avoided with this little change in the Astaro's error/block messages. I hope it gets more attention soon and, please, use big and easy to understand signs/messages to help our clever users.
That's exactly what we need! We get dozens of support tickets because of users who cannot differentiate between an error message and a blocked website!
Dennis Philpot commented
This shouldn't basicly be this hard or? Simply make the template kinda show in a Textbox where you can change your html or (i would prefere this!) make a CSS-File where you can configure everything and in the first step make it editable in a textbox.
Hope to see this feature soon.
Lutz Herzog commented
that 'd be very appreciated. I'm a little bit annoyed by the users asking me why we're blocking offline or timeouted urls.
Um, yea. I have the same issue as others have reported here, but after more than a year, doubt much will be done. This should be combined with the "Change error message" request. I already voted for that one.
I'd also like to add an email link to the admin on that page to forward that page so the admin can see at a glance what the real issue is. But it would be best if we can just code our own pages in HTML, even if we need to do it in Frontpage and import it to the Astaro. Come to think of it, a blank page with only customizable text would be better. Not ideal, but better.
Mark B. commented
Being able to have the different message pages be edited so that the visually look different to the user would help tremendously and reduce confusion for end users. Something simple like page color or background...just enough so that they see that it's something different than "denied".
Matthias Nees commented
i miss this feature also for blocked file extensions.
a localisation for blocked MIME types is also not possible (but i am not sure at what circumstances a user see a message when astaro blocked specific MIME types)
Daniel Werner commented
I agree to this feature.
I actually got a message with a screenshot. "can you whitelist this url".
A typical screenshot... "Content blocked" and a small error message "no route to host" :)
Sascha Paris commented
This seems to be a duplicate of "Change error message" which has already a lot of votes
Peter Meier commented
I always have calls from the user to ask what happen again, why the side is blocked because they don’t understand the error message. A good feature could be when the administrator can decide, maybe with a simple click, if the user should see the error from the Astaro proxy or the error from the IE. And it would be very helpful when the administrator could customize these inapprehensible messages from the Astaro proxy.
Peter Meier commented
I am absolutely agreed with Sascha Paris. I always have calls from the user to ask what happen again. A good feature could be when the administrator can decide, maybe with a simple click, if the user should see the error from the Astaro proxy or the error from the IE.
In the meantime it would be helpful to get a list with all possible errors which the Astaro proxy to display.
Sascha Paris commented
I also would like to see more detailed error messages for end users. A normal user has no idea what "transport endpoint not connected" or something similar could mean ;o))