Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 0 subscribers
  • Views 16342 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Proceed on warn button not functional

AndreH

Hey All,

Having a pretty strange issue and just checking to see if anyone else has had a similar experience as I'm not having any luck with Support.

User clicks 'proceed' after being warned about a website category - Alcohol and Tobacco in this case. For some websites, it works all the time, however, for others, it just redirects to the hostname of the web appliance. For the sites exhibiting this behaviour, we noticed that the categories are shown as "%%js_category%%" instead of Alcohol and Tobacco. We're suspecting maybe a bug on the appliance but not sure...case has been open with Support for over a month :catindifferent:

:58079


This thread was automatically locked due to age.
Parents
  • 0

    Hello itmike,

    The "%%js_category%%" error you speak of is only a cosmetic issue where the category is not displayed to the end user, and has no impact on how the policy is executed; it's only a client side javascript error.   Due to this, the defect has a lower priority compared to other defects and won't be fixed until after the 4.1 release.   There was no attempt to fix this problem in the updates in the last few weeks.

    The 4.0.4.1 release addressed the certificate issues when using a custom root CA, and certificate warnings that were appearing in MS Outlook.

    Hope that helps clear some things up for you,

    Petr.

    :58181
Reply
  • 0

    Hello itmike,

    The "%%js_category%%" error you speak of is only a cosmetic issue where the category is not displayed to the end user, and has no impact on how the policy is executed; it's only a client side javascript error.   Due to this, the defect has a lower priority compared to other defects and won't be fixed until after the 4.1 release.   There was no attempt to fix this problem in the updates in the last few weeks.

    The 4.0.4.1 release addressed the certificate issues when using a custom root CA, and certificate warnings that were appearing in MS Outlook.

    Hope that helps clear some things up for you,

    Petr.

    :58181
Children
No Data
Unfiltered HTML