HTTP Trigger not working after upgrading from v10.6 to v12.5

EYC · ‎04-09-2022

Hi all, I need help in my customized HTTP Triggers after upgrading from v10.6.1 to v12.5.1. I am not a web programmers by any standards. All my applications now instead of showing the webpages only shows HTML Codes when accessed via https://FQDN:9443/Queues

Chrome, Firefox and Edge all shows similar HTML Codes only. Only IE11 shows the intended webpage but we all know it will be EOL soon. Initially it was accessed via http://FQDN:9080/Queues but all browsers will force redirect to https://FQDN:9080/Queues throwing a SSL Error and nothing displayed. I have searched other threads and have tried https://FQDN:9443/Queues to see the HTML codes above.

Please advise what should I do to make the pages work, or what modification to the aef files or system wide parameters to be done. Thanks a lot.

bill.king1 · ‎04-10-2022

I'm not that familiar with triggers, but a couple things to start based on past posts, your Queue names don't have any special characters in them, right (that's called out specifically in the UCCX guide as far as names being an issue in version 12.5, here's a defect https://quickview.cloudapps.cisco.com/quickview/bug/CSCvx50704).

Are you able to create a new test trigger to make sure it isn't a licensing/system type issue, as opposed to something that changed as far as browser?

Can you validate the triggers to make sure no errors are reported?

EYC · ‎04-10-2022

Thanks. My CSQs only have "-" and spaces in the names. Don't think they are special characters in the KB above, I created a new HTTP trigger only to face the same issue of HTML text only on Chrome and Firefox.

bill.king1 · ‎04-11-2022

Do you have screenshots of how it looks when it works and how it does when it doesn't?

EYC · ‎04-11-2022

When using ie11, I get the regular corporate Authentication page for login via SSO. But for Chrome/Firefox/edge I just get HTML Codes

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
  <meta charset="utf-8">
  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
    
<style id="antiClickjack">
      #no-iframe { 
          display: none !important; 
      }
      #iframe {
          display: block !important;
      }
  </style>
<script type="text/javascript">
     
    if (self === top) {
       var antiClickjack = document.getElementById("antiClickjack");
       antiClickjack.parentNode.removeChild(antiClickjack);
       var removeErrorMessage = document.getElementById("antiClickjack");
    } else {
        //top.location = self.location;
    }
</script>

EYC · ‎04-12-2022

So I modified the aef script calling the any HTML file to force a content-type = text/html seems to do the trick. For whatever reasons, a content-type = text/html on the actual HTML file does not work. Only IE11 renders the HTML codes but the rest of the FF/Chrome/Edge just lists the HTML codes. Not sure if its a bug or if UCCX is setting a content-type of text/html for any HTML files.

Elliot Dierksen · ‎04-17-2022

I had the same issue after an upgrade from UCCX 10.6 to 11.6. I don't have a solution yet. The HTTP triggers I have are for a really simple dashboard. They do still render correctly in IE, but not any other browser. I am hopeful that the simple dashboards will get retired before IE goes away.