Possibility to handle errors of proxy modules within the error handler?

[holger_haas]

Hello all,

I'm trying to tweak our web gateway ruleset in a way that users will get more information why there access failed and to reduce the number of support tickets at our helpdesk.

One idea is to set a user-defined property with boolean value within the rule set and to evaluate it within the error template to decide wether this error is "worth" opening a ticket or not.

If yes, a box with link to our ticket system will be shown via java script which is otherwise not visible on the error page.

This works with "normal" rules, but as errors from the proxy module like "cannot connect" or "host not resolvable" do not appear in the error handler, I cannot use this technique for such errors.

Is it possible to include procy module errors somehow in the error handler?

Thank you and best regards,

Holger

[Former Member]

Hi Holger,

The wording of the question is a bit off.

What it sounds like you're really asking is "How to I modify the proxy generated error templates?".

You can modify the "proxy errors", all of the proxy generated errors are labeled as such in the template editor. Looking at your previous posts, you've asked about this before, so perhaps you've already done this...

See this thread:

Best Regards,

Jon

[Former Member · Accepted solution]

In case you ask though, proxy generated errors shouldnt ever fall into the error handler, the error handler is reserved for rule engine failures as opposed to proxy/networking issues.

[holger_haas]

Hello John,

ok, thank you. It's still a pity, because I wanted to avoid customizing every single error template, I justed added some java script to the "frame" template by which I can show or not show a box with debug information and link to our ticket system, dependent on the user defined variable I set in the rules. So it seems there is no way to use this technique with proxy generated errors.

Best Regards,

Holger

[Former Member]

Hi Holger,

You shouldnt need to customize every template. Check out the PreConfig (built by Erik). https://mcafee.app.box.com/mwg-preconfig

He does something similar for avoiding the site review, I believe all of this is done based on the template language.

Best Regards,

Jon

[eelsasser]

The PreConfig is no longer posted to the public on Box.

However, here is a canned "System" template collection extracted from it that you can import.

It's just a different looking style than the other pages so the user doesn't see the same pages as the normal block pages you have.

You can set all of the proxy-generated messages to this collection and keep separate from your others.

e²