PingAuthorize

HTTP caching

The Policy Editor transfers data through HTTP APIs.

To improve page loading speeds, the Policy Editor uses HTTP headers to cache the API responses for the following URLs:

  • /app/trust-framework/*

  • /app/policy-manager/*

  • /app/test-suite/*

HTTP caching is enabled by default.

When hosting the Policy Editor using a self-signed SSL certificate, browsers like Google Chrome and Microsoft Edge don’t include the caching HTTP headers. Customers with such deployments can use a different browser, such as Mozilla Firefox, to observe the performance benefits.

You can disable HTTP caching persistently by providing the --disableApiHttpCache option when running setup. Caching remains disabled for future server starts and stops. The following example illustrates this option:

bin/setup demo \
--disableApiHttpCache \
--adminUsername admin \
--generateSelfSignedCertificate \
--decisionPointSharedSecret 2FederateM0re \
--hostname example.com \
--port 9443 \
--adminPort 9444

To disable HTTP caching for a single server start, provide the PING_ENABLE_API_HTTP_CACHE=false environment variable when running start-server, as illustrated in the following example:

env PING_ENABLE_API_HTTP_CACHE=false bin/start-server

To temporarily re-enable HTTP caching after using the –-disableApiHttpCacheoption, provide the PING_ENABLE_API_HTTP_CACHE=true environment variable when running start-server.

To persistently re-enable HTTP caching after using the --disableApiHttpCacheoption, delete the setup output (the configuration.yml file and key stores generated during setup). Then, reconfigure the server by running setup.