Browser Support

The Scout HTML UI requires a web browser with modern built-in technologies: HTML 5, CSS 3, JavaScript (ECMAScript 5). Scout does its best to support all browsers widely in use today by making use of vendor-specific prefixes, polyfills or other workarounds. However, some older or obscure browsers are not supported deliberately, simply because they are lacking basic capabilities or the required effort would be beyond reason.

Here is a non-exhaustive list of supported browsers:

Desktop

  • Mozilla Firefox >= 69

  • Chromium (like Google Chrome, Microsoft Edge, Brave or Opera) >= 71

  • Apple Safari >= 13

Mobile

(Due to the nature of mobile operating systems, it is hard to specify exact versions of supported browsers. Usually, the screen size and the device speed are the limiting factors.)

  • iOS >= 13

  • Android >= 5

HTTP/2

Starting with Scout 24 HTTP/2 is supported and highly recommended to be used! HTTP/2 can use multiplexing for multiple requests over a single TCP connection which eliminates the issue that only a few number of tabs can be open in the Browser for the same Scout application.

To ensure HTTP/2 is used for the Browser running your Scout application the following should be considered:

  • HTTP/2 is only used by Browsers when the requests are encrypted (https). Therefore, ensure your application is only accessible using TLS (which is recommended anyway).

  • HTTP/2 must be enabled on the server that accepts the requests from the Browser. This may be a WAF, Load balancer, or Reverse Proxy in front of your Scout application (for best security it is not recommended to expose the Scout server directly to the Internet). Please consult the documentation of your proxy or WAF on how to activate HTTP/2 and https.

  • You may also use HTTP/2 from the front-end proxy or WAF to the actual Scout Jetty server but this is optional.

  • The Scout Jetty server supports HTTP/2 since version 24 out of the box.