Changes between Version 1 and Version 2 of Ticket #3056, comment 13


Ignore:
Timestamp:
09/16/2015 09:34:16 AM (4 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3056, comment 13

    v1 v2  
    33Enabling multi-threading seems to be the appropriate solution here. That way the server can handle multiple connections at the same time. 
    44 
    5 Alternatively, we could add the `Connection: close` header ~~to force the browser to close the connection after every request. This however, might slow down other use cases.~~ Chrome, at least, seems to ignore the `Connection: close` header, leaving the connection open until its closed by the server or until there are no more requests to send. 
     5Alternatively, we could add the `Connection: close` header ~~to force the browser to close the connection after every request.~~ But Chrome seems to ignore the `Connection: close` header, leaving the connection open until its closed by the server or until there are no more requests to send. However, disabling keep-alive would be another difference to the production server that we should avoid anyway.