# Litium back office, expected to work in Microsoft Internet Explorer and Edge?

**URL:** <https://forum.litium.com/t/litium-back-office-expected-to-work-in-microsoft-internet-explorer-and-edge/139>\
**Category:** Questions\
**Created:** [July 3, 2018, 6:33am UTC](https://forum.litium.com/t/litium-back-office-expected-to-work-in-microsoft-internet-explorer-and-edge/139 "2018-07-03T06:33:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MagnusK](https://avatars.discourse-cdn.com/v4/letter/m/f9ae1b/32.png) [@MagnusK](https://forum.litium.com/u/MagnusK)\
**Post date:** [July 3, 2018, 6:33am UTC](https://forum.litium.com/t/litium-back-office-expected-to-work-in-microsoft-internet-explorer-and-edge/139/1 "2018-07-03T06:33:42Z")

</div>

Hi all,

We are experiencing very mixed response when using Litium Backoffice from different web browsers.

Chrome = seems really fast  
Microsoft Edge = really slow, loads web page in web site administration in 20-25 seconds, if they are even displayed (stops loading after 30 secs)

I saw on the Requirements page for Litium that Internet Explorer latest version is supposed to work, is MS Edge included in that statement?

Litium version: 6.1.1

Regards  
Magnus

---

<div class="post-metadata">

**Author:** ![patric.forsgard](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.litium.com/patric.forsgard/32/10_2.png) [@patric.forsgard](https://forum.litium.com/u/patric.forsgard)\
**Post date:** [July 5, 2018, 7:59am UTC](https://forum.litium.com/t/litium-back-office-expected-to-work-in-microsoft-internet-explorer-and-edge/139/2 "2018-07-05T07:59:27Z")

</div>

Back office is working in Microsoft Edge.

_In this specific case the site is running behind a CDN network to get faster access around the world._

In back office the product is using signalR for pushing events from the server to the client. The CDN provider is not supporting `websockets` and Edge browser was falling back to use `long polling`. When the request should be sent to server the CDN was finding that it already existed an open connection to the server and was waiting for that to complete before processing the new request. This wait-time was causing the latency in request/responses. After reconfiguration of the CDN provider the signalR events will bypass the caches and is sent directly to the origin server.

For other browser the fallback from `websockets` was into `event stream` that the CDN provider supports.

Edge and some other browser are not supporting `event stream`, see full table on [https://caniuse.com/#feat=eventsource](https://caniuse.com/#feat=eventsource)
