cancel
Showing results for 
Search instead for 
Did you mean: 
crehwoldt
Level 7

WebGateWay-property in Template

Hi,

I've changed the default template (default Schema / en / html) to add our company name / logo and to link to our comapny acceptable use policy.

I've also added a html part that allows the user to automatically create a ticket for our help desk system. This is a special URL that creates a new support ticket.

I use some WebGateWay properties to get more information for the ticket :  http://<ip of our help desk system>/create.php?init&title=WebGateWay : $Block.Reason$&text=Block ID : $Block.ID$\nReason : $Block.Reason$ ...

This works great for "blocked" sites (URL Filter, Certificate, ...) but if there is a "real" error like "Bad Gateway" or "Bad Request" i always get (of course) "Block Reason:0"

Is there any property that contains the error or templatename?

Thank you

Christian

Nachricht geändert durch crehwoldt on 18.07.11 08:53:32 CDT
0 Kudos
4 Replies
asabban
Level 17

Re: WebGateWay-property in Template

Hi Christian,

you can try to utilize the

Message.TemplateName

property. Maybe it gives you a start.

best,

Andre

0 Kudos
crehwoldt
Level 7

Re: WebGateWay-property in Template

asabban schrieb:

Hi Christian,

you can try to utilize the

Message.TemplateName

property. Maybe it gives you a start.

best,

Andre

Hi,

its strange..."Message.TemplateName" doesn't work for the "real" errors. It shows me onyl the templatename for URL filter errors.

Thanks

Christian

0 Kudos
eelsasser
Level 15

Re: WebGateWay-property in Template

You may be doing this already and didn't mention it, but in case you are not, I'd recommend enclosing the properties in

$String.URLEncode($somePropertyName$)$

In case there are illegal characters in the URL you are passing (like spaces), this should convert them to legal values when passed in a URL.

0 Kudos
crehwoldt
Level 7

Re: WebGateWay-property in Template

eelsasser schrieb:

You may be doing this already and didn't mention it, but in case you are not, I'd recommend enclosing the properties in

$String.URLEncode($somePropertyName$)$

In case there are illegal characters in the URL you are passing (like spaces), this should convert them to legal values when passed in a URL.

No, I didnt. Thank you.

Christian

0 Kudos