Selexor loads very slow on some browsers

[linkleonard]

Reported by llaw02 on 18 Apr 43357409 21:17 UTC
When loading the web page for selexor on Chrome, it may take a >10 seconds before the user sees something on the screen.

There are two underlying issues:

---

This has been identified as a chrome issue:

https://code.google.com/p/chromium/issues/detail?id=195550#c11

Modern browsers perform pre-connections to web servers when they anticipate that multiple files are going to be requested from the web server. Since the selexor was initially single threaded, it can only handle one connection at a time. The extra preconnections don't actually send any data over initially, so after the first connection is served, if they somehow become the active connection that is being handled, selexor blocks until it times out, effectively being a race condition.

---

The length of the message was not sent over from selexor to the client. Web browsers expect the length of a response when performing a request. This causes them to wait until a timeout to occur.