KB Article #183176

API Portal performance issue caused by https://cdn.axway.com/ux/icons/font/style.css

Problem

If you experience performance issue in API Portal, one possible reason could be the request for https://cdn.axway.com/ux/icons/font/style.css Since this resource is no longer needed and from 7.7 February 2024 the request for it is removed, in this KB we will show how to manually remove it for older releases.

Resolution

  1. Login to JAI
  2. Go to System > Site Template Styles
  3. Open T4 - Page Builder or your copy of this style if you have customized it.
  4. From the left sidebar click on Global Settings > Custom code
  5. From the "Before </head>" section, remove the following line and click Save:
<link href="https://cdn.axway.com/ux/icons/font/style.css" rel="stylesheet">

If you are using T4 template

  1. Login to JAI
  2. Go to System > Plugins > System - HTTP Headers
  3. Go to Content-Security-Policy (CSP) tab
  4. Scroll to policy directives list and remove https://cdn.axway.com/ux/icons/font/style.css from style-src-elem policy directive
  5. Remove https://cdn.axway.com/ux/icons/font/fonts/ from font-src policy directive

If you are using T4 template and CSP is not enabled from System - HTTP Headers plugin:

  1. Login to JAI
  2. Go to System > Plugins > System - HTTP Headers
  3. Go to Content-Security-Policy (CSP) tab
  4. Enable CSP toggle
  5. Disable Report-only toggle
  6. Enable Nonce toggle
  7. Click on Add directive button
  8. For policy directive set style-src-elem
  9. For value set
'self' https://fonts.googleapis.com https://cdnjs.cloudflare.com/ajax/libs/font-awesome/ 'unsafe-inline'

If you are using Purity III template

For API Portal releases prior to May 2023

  1. Login to JAI
  2. Go to System > Plugins > API Portal - System
  3. Remove https://cdn.axway.com from Content Security Policy field and save.

For API Portal releases from May 2023 and after that follow the process from "If you are using T4 template" section

After that https://cdn.axway.com/ux/icons/font/style.css should no longer cause performance issues